- Can I use startsevdenis/liform-bundle in a Laravel application?
- Not as a drop-in package. LiformBundle is a Symfony bundle built around the Symfony kernel, bundle registration, and container compilation, so Laravel has no bundle bootstrapping or auto-discovery for it. You would need to extract the underlying generator and bind it in a Laravel service provider, or fork the wrapper. Budget for an adapter rather than a normal Composer install.
- How do I install LiformBundle?
- In a Symfony app you install it with Composer and register the bundle in bundles.php, following Symfony bundle conventions. In Laravel there is no service provider, config publishing, or package discovery, so composer require alone will not wire it up. You would need an app-level provider or a build-time command to use the underlying schema generation.
- Does LiformBundle support Laravel 10 or Laravel 11?
- There is no official Laravel support stated; the package is a Symfony bundle, not a Laravel package. Laravel version compatibility is therefore not the relevant constraint. The practical question is whether the underlying form-to-JSON-Schema generator can run standalone on your PHP version alongside Laravel's dependencies.
- Does LiformBundle require Symfony Form?
- Yes, the value of the bundle depends on Symfony Form definitions, because it translates form types, constraints, and metadata into JSON Schema. Laravel does not use symfony/form in its request validation path, so adopting it means introducing Symfony Form as a parallel form-definition system. That creates a second source of truth next to Laravel FormRequest and validation rules.
- How does LiformBundle map validation constraints to JSON Schema?
- The bundle maps Symfony form constraints and metadata into schema output so client-side renderers can reflect backend rules. The assessment flags incomplete mapping of custom form types and constraints as a risk to verify. Test your own constraint set rather than assuming full coverage.
- Can I generate JSON Schema from Laravel with an artisan command?
- Yes, that is the preferred integration shape described in the assessment: an artisan schema:generate command that runs at build time and writes JSON Schema artifacts. It isolates the Symfony dependency to a dev or build context and keeps it out of the request hot path. You would author form types outside the request lifecycle and invoke the underlying generator, not the bundle.
- Is LiformBundle actively maintained and production-ready?
- The assessment reports zero stars, zero dependents, and a single-maintainer release cadence, with no community validation or evidence of production hardening. That is a high provenance risk even though the generation path is read-only and offline. Treat it as an unproven candidate implementation and plan to own the wrapper code you rely on.
- What JSON Schema draft does LiformBundle emit?
- The provided assessment flags JSON Schema draft-version ambiguity as a secondary risk, so the draft is not clearly established. You should inspect the emitted schema and the underlying generator's configuration before downstream consumers depend on it. Draft differences affect $ref handling, definitions, and validator behavior.
- What are alternatives to LiformBundle for Laravel?
- The assessment suggests depending directly on the underlying generator rather than the bundle, or extracting a small Laravel service provider around it. Other options include defining JSON Schema artifacts explicitly, generating them from Laravel validation rules, or using an OpenAPI-first workflow. The key is to avoid maintaining two independent form-definition systems.
- How should I test JSON Schema generated by LiformBundle?
- Use representative form types, including custom types and constraints, and assert schema output snapshots rather than only smoke-testing the service. The assessment asks whether the package's own tests assert schema snapshots or just exercise the service. Validate emitted schemas against the draft you intend to support and test downstream consumers against them.