Feature: Product option types to support multiple cases

src/Catalog/ProductOptionTypeInterface.php

@@ -1,34 +0,0 @@
-<?php
-
-namespace Modules\Core\Catalog;
-
-use Filament\Forms\Components\Component;
-
-/**
- * A Product Option Type describes how a category of Lunar `ProductOption` (e.g.
- * "Color", "Size", "Material") behaves — namely, what structured data its values
- * carry in their free-form `meta` jsonb column, and how an admin edits that data.
- *
- * `ProductOption`/`ProductOptionValue` themselves stay exactly as Lunar defines
- * them — this is not a new model, just a registry (ProductOptionTypeRegistry) that
- * maps a `ProductOption::handle` to the type describing it, so adding a new kind of
- * option (a new color-like or size-like concept) is a single new class, not scattered
- * per-option special-casing across the admin UI or storefront.
- */
-interface ProductOptionTypeInterface
-{
-    /**
-     * Matches the ProductOption::handle this type describes (e.g. 'color', 'size').
-     */
-    public static function getKey(): string;
-
-    /**
-     * Filament form components for editing a ProductOptionValue's `meta` under this
-     * option type — e.g. Color returns a color picker for `meta.hex`, Size returns a
-     * numeric input for `meta.sort_value`. Field names should be dot-notation under
-     * `meta` (e.g. `meta.hex`), matching where ValuesRelationManager's form saves them.
-     *
-     * @return array<Component>
-     */
-    public function getMetaForm(): array;
-}