- Can I use atoolo/form-bundle directly in a Laravel application?
- Not natively. atoolo/form-bundle is a Symfony bundle built around Symfony 6.3+ or 7.0+ components and does not ship Laravel service providers, FormRequest hooks, or Blade integration. The realistic path is to run it as a headless HTTP service or embed a Symfony microkernel and call it from Laravel. Treat any native Laravel use as a custom integration project, not a drop-in Composer install.
- What does atoolo/form-bundle actually do?
- It provides an HTTP interface for displaying and processing forms using JSON Forms, a declarative schema-based approach. That makes it useful for complex dynamic forms such as admin panels, configurable inputs, and multi-step workflows. For simple CRUD forms it is likely overkill compared with native Laravel form tooling.
- Which Laravel versions work with atoolo/form-bundle?
- There is no official Laravel version support because the package targets Symfony 6.3+ or 7.0+. If you consume it as a microservice over HTTP, any Laravel version with a capable HTTP client can call it. If you attempt a Symfony-Laravel bridge, compatibility depends on your bridge code and Symfony runtime, not on a Laravel support matrix.
- How do I install atoolo/form-bundle?
- Install it with Composer into a Symfony application, for example composer require atoolo/form-bundle, and wire the bundle into the Symfony kernel. It is not installed as a Laravel package with auto-discovery service providers. For Laravel, install and run it in a separate Symfony service, then call the exposed form endpoints from your Laravel app.
- Is atoolo/form-bundle stable enough for production?
- The latest release is 1.0.0-beta.4, so there is no stable 1.x release yet. The project also shows very low adoption, which raises abandonment and breaking-change risk. Use it first for a non-critical form, pin the exact version, and keep a fallback plan before relying on it in production.
- What are the best alternatives to atoolo/form-bundle for Laravel forms?
- For simpler needs, use Laravel-native options such as Laravel Collective, Livewire forms, Nova forms, or spatie/laravel-forms. If you want JSON Forms-style schemas, you can pair a JavaScript JSON Forms frontend with a Laravel backend instead of adopting a Symfony bundle. Choose atoolo/form-bundle only when its schema-driven HTTP form processing is worth the hybrid stack.
- How should I handle authentication and authorization with atoolo/form-bundle?
- If you use it as a microservice, protect the Symfony form endpoints with service-to-service authentication and keep them off the public internet. In Laravel, enforce user authorization with middleware before proxying requests to the form service. Avoid mixing Symfony security assumptions with Laravel sessions unless you have explicitly designed that bridge.
- Does atoolo/form-bundle support complex validation and multi-step forms?
- JSON Forms uses JSON Schema and UI Schema to describe form structure and validation, so complex and multi-step workflows are within its design scope. The bundle's HTTP interface handles display and processing, but the exact validation behavior depends on your schemas and processing rules. Test validation edge cases carefully, especially across the Laravel-to-Symfony boundary.
- How do I test a Laravel integration with atoolo/form-bundle?
- Start with a single non-critical form and test the HTTP contract between Laravel and the Symfony service. Use Laravel's HTTP client fakes for unit tests and contract tests against a real running service for schema and validation behavior. Verify JSON schema responses, error handling, authentication, and timeout behavior before expanding to more forms.
- What are the performance and maintenance risks of atoolo/form-bundle in a hybrid Laravel stack?
- Running Symfony dependency injection and event dispatch alongside Laravel can add latency and operational complexity, so cache form definitions where possible. The bigger risk is maintenance: a beta release, zero stars, and limited dependents mean upgrades and abandonment need a backup plan. Budget for a hybrid-stack owner and avoid coupling critical Laravel workflows to this bundle early.