Laravel Crud Forms Laravel Package

Getting Started

• Install with Composer using the new 9.0 line: composer require achillesp/laravel-crud-forms:^9.0.
• Confirm runtime requirements before upgrading:
  • PHP 8.2+ for Laravel 11 or 12.
  • PHP 8.3+ for Laravel 13.
• Check composer.json for Laravel framework constraints; 9.0 supports Laravel 11, 12, and 13 from a single release line, so the package should resolve for any of those versions.
• Start by reviewing the package README/CHANGELOG and service provider/config. Publish any package config or assets if the package documents publish tags, then verify the published files are under version control where appropriate.
• First use case: wire a simple CRUD resource — for example a Post form — into a controller and Blade view, using Laravel Form Requests for validation and the package’s form/field definitions for rendering and persistence.

Implementation Patterns

• Use ^9.0 consistently across Laravel 11, 12, and 13 applications. The compatibility promise is version-line based, not framework-specific package branches.
• In CI, test the actual framework/PHP combinations you deploy:
  • Laravel 11 + PHP 8.2+
  • Laravel 12 + PHP 8.2+
  • Laravel 13 + PHP 8.3+
• Keep CRUD form definitions close to the resource: controller actions handle authorization and validation, while reusable form/field configuration handles presentation and input mapping.
• Prefer Laravel-native integration points: Form Requests for validation, policies/gates for authorization, route model binding for edit/update/delete flows, and resource controllers for conventional CRUD routes.
• When upgrading from 8.0, treat this primarily as a compatibility release: update Composer constraints, run the test suite, and smoke-test create/edit/delete forms on the target Laravel version.
• If the package exposes configurable views/components, override them in application-level view paths rather than editing vendor files.

Gotchas and Tips

• The main upgrade trap is PHP version mismatch: Laravel 13 requires PHP 8.3+, even though the same package line still supports Laravel 11/12 on PHP 8.2+.
• If Composer resolves an older package version unexpectedly, inspect with composer why-not achillesp/laravel-crud-forms 9.0 and check PHP/platform and Laravel framework constraints.
• Be explicit in CI about the PHP version used for Laravel 13. A matrix that tests Laravel 13 on PHP 8.2 will fail dependency resolution.
• Because one release line spans Laravel 11–13, avoid assuming Laravel 13-only APIs are required or available in application code shared across versions.
• After upgrading, clear cached config/routes/views and verify package discovery, published config, and any published views or migrations.
• For debugging, use composer show achillesp/laravel-crud-forms, php artisan about, and targeted form/request tests. Check package config and view overrides first when rendering or validation behavior changes.
• Extension points to prefer: package config, published views/components, custom field/form classes where documented, and Laravel validation/authorization layers. Avoid editing vendor code so future compatibility updates remain safe.