Form Bundle Laravel Package

## Technical Evaluation

### **Architecture Fit**
- **Symfony 8 Bundle**: The package is a **Symfony 8 bundle**, meaning it integrates seamlessly with Symfony’s ecosystem (Dependency Injection, Event Dispatcher, Validator, etc.). This aligns well with Laravel’s **Lumen** or **Symfony-based Laravel** (e.g., via **Laravel Symfony Bridge** or **API Platform**).
- **JSON-First API Forms**: The bundle’s focus on **JSON-first API form handling** (RFC 9457 Problem Details, Doctrine validation, data transformers) is a **strong fit** for Laravel’s API-first applications, particularly those using **Laravel Sanctum, Passport, or API Resources**.
- **Controller Traits & Form Types**: The inclusion of **controller traits** and **custom form types** suggests a **declarative approach** to form handling, which can reduce boilerplate in Laravel’s **resource controllers** or **API middleware**.
- **Doctrine Validation**: While Laravel primarily uses **Laravel Validation**, this bundle’s **Doctrine-based validation** could be adapted via **Doctrine ORM integration** (if using **Laravel Doctrine** or **Eloquent Doctrine Bridge**).

### **Integration Feasibility**
- **Symfony vs. Laravel Compatibility**:
  - Laravel’s **Service Container** is **PSR-11 compliant**, but Symfony’s **Dependency Injection** has subtle differences (e.g., `services.yaml` vs. Laravel’s `config/services.php`).
  - The bundle’s **autowiring** and **autoconfiguration** can be replicated in Laravel via **package discovery** and **service providers**.
- **Key Components to Adapt**:
  - **Form Types** → Laravel **Form Requests** or **API Resources**.
  - **Problem Details (RFC 9457)** → Laravel’s **API Error Responses** (can be extended via **Exception Handlers**).
  - **Data Transformers** → Laravel’s **Accessors/Mutators** or **API Resource Transformers**.
  - **Doctrine Validation** → Laravel’s **Validator** or **Custom Rules**.
- **Potential Challenges**:
  - **Symfony Event System** → Laravel uses **Events & Listeners**, but integration is possible via **Symfony EventDispatcher** in Laravel.
  - **Kernel & Bundle Structure** → Laravel’s **Service Provider** model differs from Symfony’s **Bundle** system, requiring a **wrapper layer**.

### **Technical Risk**
| **Risk Area**               | **Assessment**                                                                 | **Mitigation Strategy**                                                                 |
|-----------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
| **Symfony-Specific Abstractions** | Heavy reliance on Symfony’s `Form`, `Validator`, and `EventDispatcher`.       | Use **Laravel Symfony Bridge** or **API Platform** for compatibility.                   |
| **Doctrine ORM Dependency**  | Laravel primarily uses Eloquent; Doctrine integration may require extra work. | Use **Eloquent Doctrine Bridge** or **Laravel Doctrine** if ORM is needed.               |
| **Problem Details (RFC 9457)** | Laravel’s default error format differs from RFC 9457.                         | Extend Laravel’s `App\Exceptions\Handler` to match RFC 9457.                          |
| **Controller Traits**       | Laravel prefers **Service Classes** over traits in controllers.               | Refactor traits into **Laravel Services** or **Middleware**.                           |
| **Testing Complexity**      | Integration tests assume Symfony Kernel; Laravel’s testing differs.           | Mock Symfony services or use **PestPHP** for hybrid testing.                          |

### **Key Questions for TPM**
1. **Is this for a new Laravel API or an existing Symfony-integrated project?**
   - If **new Laravel API**, assess whether **Symfony dependencies** are justified.
   - If **Symfony-integrated**, leverage **Laravel Symfony Bridge** for smoother adoption.
2. **Do we need Doctrine ORM, or can we use Eloquent + Custom Validation?**
   - If **Eloquent**, adapt validation logic to Laravel’s **Validator**.
3. **How critical is RFC 9457 Problem Details compliance?**
   - If **non-negotiable**, extend Laravel’s error handling.
   - If **flexible**, use Laravel’s default JSON responses.
4. **Will this replace Laravel’s Form Requests or augment them?**
   - If **replacement**, expect refactoring of existing controllers.
   - If **augmentation**, use **mixins** or **decorators**.
5. **What’s the team’s familiarity with Symfony’s DI/Events?**
   - Higher familiarity → **faster adoption**.
   - Lower familiarity → **expect training or abstraction layers**.

---

## Integration Approach

### **Stack Fit**
| **Laravel Component**       | **Bundle Component**               | **Integration Strategy**                                                                 |
|-----------------------------|-------------------------------------|-----------------------------------------------------------------------------------------|
| **Laravel Validation**      | Doctrine Validation                | Use **Laravel’s Validator** + **Custom Rules** or **Doctrine Validator via Bridge**.   |
| **Form Requests**           | API Form Types                     | Convert Symfony `FormType` to Laravel **Form Requests** or **API Resources**.           |
| **API Resources**           | Data Transformers                  | Use Laravel’s **Accessors/Mutators** or extend `JsonResource`.                          |
| **Exception Handler**       | RFC 9457 Problem Details           | Extend `App\Exceptions\Handler` to format errors per RFC 9457.                          |
| **Service Container**       | Symfony DI                          | Use **Laravel’s Service Providers** to register Symfony services.                       |
| **Events & Listeners**      | Symfony EventDispatcher            | Use **Laravel Events** or wrap Symfony `EventDispatcher` in a Laravel service.          |

### **Migration Path**
1. **Phase 1: Proof of Concept (PoC)**
   - Install bundle in a **separate Laravel project** (e.g., `laravel-symfony-poc`).
   - Test **core features** (Form Types, Validation, Problem Details).
   - Benchmark **performance vs. native Laravel solutions**.
2. **Phase 2: Abstraction Layer**
   - Create a **Laravel wrapper package** (e.g., `laravel-form-bundle-adapter`) to:
     - Convert Symfony `FormType` → Laravel `FormRequest`.
     - Adapt Doctrine Validation → Laravel Validation.
     - Wrap `EventDispatcher` for Laravel compatibility.
3. **Phase 3: Incremental Adoption**
   - Start with **non-critical API endpoints**.
   - Gradually replace **Form Requests** with bundle-powered forms.
   - Use **feature flags** to toggle bundle vs. native Laravel logic.

### **Compatibility**
| **Compatibility Check**          | **Result**                                                                 | **Workaround**                                                                          |
|-----------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
| **PHP 8.1+ Support**              | ✅ Bundle requires PHP 8.1+ (matches Laravel 9+).                          | No action needed.                                                                       |
| **Symfony 6.4+ Dependency**       | ⚠️ Laravel may not have all Symfony 6.4 packages.                          | Use **Symfony Flex** or **Composer overrides** to install missing packages.           |
| **Doctrine ORM**                   | ❌ Laravel uses Eloquent by default.                                       | Use **Eloquent Doctrine Bridge** or stick to Laravel Validation.                        |
| **Symfony EventDispatcher**       | ⚠️ Laravel has its own event system.                                       | Create a **Symfony-to-Laravel event bridge**.                                           |
| **Problem Details (RFC 9457)**    | ❌ Laravel’s default JSON errors differ.                                   | Extend `App\Exceptions\Handler` to match RFC 9457.                                      |

### **Sequencing**
1. **Step 1: Dependency Setup**
   - Install bundle via Composer:
     ```bash
     composer require chamber-orchestra/form-bundle
     ```
   - Publish bundle config (if needed) via:
     ```bash
     php artisan vendor:publish --provider="ChamberOrchestra\FormBundle\FormBundle"
     ```
2. **Step 2: Core Integration**
   - Register Symfony services in `config/services.php`:
     ```php
     $app->singleton(SymfonyEventDispatcher::class, fn() => new EventDispatcher());
     ```
   - Create a **Laravel Service Provider** to bridge Symfony and Laravel:
     ```php
     class FormBundleServiceProvider extends ServiceProvider {
         public function register() {
             $this->app->singleton('symfony.form.type_registry', fn() => new FormTypeRegistry());
         }
     }
     ```
3. **Step 3: Form Handling**
   - Convert Symfony `FormType` to Laravel `FormRequest`:
     ```php
     // Symfony FormType
     class UserType extends AbstractType {
         public function buildForm(FormBuilderInterface $builder, array $options) { ... }
     }

     // Laravel Form Request
     class StoreUserRequest extends FormRequest {
         public function rules() {
             return [
                 'name' => 'required|string',
                 'email' => 'required|email',
             ];
         }
     }
     ```
4. **Step 4: Error Handling**
   - Extend Laravel’s `App\Exceptions\Handler` to support RFC