Repository Forms Laravel Package

Technical Evaluation

Architecture Fit

• Laravel Compatibility (Unchanged): The package remains fundamentally tied to eZ Platform’s repository API and Symfony’s ecosystem. No changes in v2.5.15 alter this core misalignment.

  • Key Misalignment:
    • Still relies on eZ Publish’s ContentService and Symfony DI, incompatible with Laravel’s Eloquent/Blade stack.
    • Form abstraction layer (e.g., FormRepository) is eZ-specific, with no Laravel equivalents.
  • Potential Workarounds (Unchanged):
    • Could serve as reference architecture for a custom Laravel form repository, but requires full refactoring.
    • Symfony Bridge remains the only theoretical integration path, with high refactoring costs.

• Use Case Overlap (Unchanged):

  • Laravel’s FilamentPHP, Nova, or Spatie Form Builder remain superior for dynamic forms.
  • No new features in v2.5.15 address Laravel’s needs (e.g., Blade integration, Eloquent support).

Integration Feasibility (Unchanged)

• Direct Integration: Still low feasibility due to:
  • No Laravel-specific APIs added in this release.
  • Symfony dependencies (e.g., ezpublish-api) remain incompatible with Laravel’s container.
• Indirect Integration (Updated):
  • No new hooks or abstractions in v2.5.15 to simplify extraction of form logic.
  • Validation/field systems could still be ported manually, but no tooling assistance exists.

Technical Risk (Updated)

Key Questions (Updated)

1. Why Laravel? (Reiterated)

   • Is the goal to replace eZ Platform entirely, or integrate its forms via API?
   • New Subquestion: Given the release’s lack of updates, is eZ Platform’s form system actively maintained for future Laravel compatibility?

2. Feature Parity Needs (Reiterated)

   • Which specific ezsystems/repository-forms features are non-negotiable?
   • Example: If workflow-based forms (e.g., eZ’s ContentState integration) are critical, Laravel lacks native equivalents (e.g., Laravel Nova Actions are limited).

3. Long-Term Viability (Updated)

   • Added: With no updates in 2.5.x, is this package abandoned? If so, fork and adapt for Laravel or migrate to alternatives like FilamentPHP.
   • Would a custom Laravel package (e.g., laravel-form-repository) be more sustainable than maintaining a legacy dependency?

4. Team Expertise (Reiterated)

   • Does the team have Symfony/eZ Platform skills to bridge the gap?
   • New Consideration: If not, cost of hiring consultants may outweigh benefits of this package.

Integration Approach

Stack Fit (Unchanged)

• Laravel’s Native Alternatives:

  • FilamentPHP (admin panels), Livewire (reactive forms), or Spatie Laravel Form Builder remain the only viable paths.
  • No changes in v2.5.15 justify using ezsystems/repository-forms.

• Symfony Bridge (Unchanged):

  • Still requires manual isolation of Symfony components (e.g., symfony/validator).
  • No new Laravel-Symfony interop tools introduced.

Migration Path (Updated)

Compatibility (Unchanged)

• High Risks:
  • Service Container: Still incompatible.
  • Routing/Events: No Laravel equivalents for eZ’s Route or event system.
• Low Risks:
  • Validation Logic: Can be manually ported to Laravel’s Validator.

Sequencing (Updated)

1. Phase 1: Proof of Concept (2-4 weeks)

   • Updated: Abandon direct integration—instead, build a minimal Laravel form system using Spatie/FilamentPHP to replicate 1-2 eZ form types.
   • Goal: Prove Laravel alternatives can fulfill 80% of needs without ezsystems/repository-forms.

2. Phase 2: Core Integration (4-8 weeks)

   • Updated: If critical eZ features (e.g., workflows) are missing, fork the package and adapt it for Laravel’s stack.
     • Example: Replace ezpublish-api with Laravel service bindings.
   • Alternative: Use eZ as a headless CMS via API, with Laravel handling forms.

3. Phase 3: Full Migration (8+ weeks)

   • Updated: Deprecate ezsystems/repository-forms entirely—no updates in 2.5.x justify continued dependency.
   • Replace all form-related logic with Laravel-native solutions.

4. Phase 4: Optimization

   • No change: Benchmark Laravel alternatives (e.g., Livewire vs. FilamentPHP).

Operational Impact

Maintenance (Updated)

• Short-Term:
  • High effort if attempting to integrate ezsystems/repository-forms.
  • Added: No updates in 2.5.x suggest no future maintenance from the eZ team—increase risk of technical debt.
• Long-Term:
  • Lower maintenance with Laravel-native solutions.
  • Added: Forking the package adds extra burden—only justified for unique eZ features with no Laravel alternative.

Support (Updated)

• Community:
  • No change: Limited support for Laravel use.
  • Added: No release notes or updates in 2.5.x imply abandoned or low-priority—risk of unpatched vulnerabilities.
• Vendor Lock-in:
  • No change: eZ Platform’s ecosystem is niche; Laravel’s is enterprise-ready.
  • Added: No roadmap for Laravel compatibility—avoid dependency.

Scaling (Unchanged)

• Performance:
  • Laravel’s Eloquent + caching (Redis) can match eZ’s repository layer for CRUD.
• Horizontal Scaling:
  • Laravel’s queue workers (e.g., for form submissions) scale better than eZ’s event system.

Failure Modes (Updated)