Weave Code
Form Bundle Laravel Package
sbsedv/form-bundle
A Symfony bundle for working with forms, providing reusable form types, extensions, and helpers that reduce boilerplate and keep form configuration consistent across applications. Built to integrate smoothly with Symfony’s Form component and common form workflows.
A Symfony bundle that adds some usefull symfony/form integrations.
Frequently asked questions about Form Bundle
- Is sbsedv/form-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It ships a bundle class and a dependency-injection extension and relies on Symfony's Form component and tag-based registration. Laravel has no equivalent bundle bootstrap, so you cannot adopt it as a drop-in Laravel dependency.
- How do I install sbsedv/form-bundle with Composer?
- Install via Composer using composer require sbsedv/form-bundle. In a Symfony app you then enable the bundle in bundles.php and configure it through the bundle's DI extension. In Laravel you would also need to add symfony/form and register form types manually because the bundle's automatic tag collection will not run.
- Does sbsedv/form-bundle support Laravel 10, 11, or 12?
- There is no first-party Laravel support; it is built for Symfony's Form component. Laravel 10, 11, and 12 do not depend on symfony/form by default, so integration is additive and requires custom glue. You would own a service provider that registers form types and extensions manually.
- What does the Symfony 8 support change in v1.10.0 mean for my app?
- v1.10.0 only widens the Symfony constraint to allow Symfony 8; it adds no features or API changes. Existing installs on Symfony 6 or 7 should resolve unchanged. If Composer selects Symfony 8, verify the PHP floor, which is likely PHP 8.4 or higher for Symfony 8.
- Can I use sbsedv/form-bundle in Laravel without Symfony?
- No. The bundle's value lives in Symfony's Form component, including form types, extensions, and tag-based discovery. Laravel does not ship that machinery, so a Laravel-only app has nothing for the bundle to hook into. You would need to pull in symfony/form and hand-wire the registrations.
- What is the integration effort for using this bundle in a Laravel application?
- Feasible but non-trivial: add symfony/form, then manually register the bundle's form types and extensions in a Laravel service provider. The bundle's automatic tag collection will not run under Laravel, so that glue becomes your code to maintain. Budget for niche debugging because Symfony Form wiring inside Laravel is thinly documented.
- Are there Laravel adapters or alternatives for sbsedv/form-bundle?
- There are no known first-party or community Laravel adapters for this bundle. For Laravel-first teams, native Laravel validation and form request patterns are usually the better fit. If you need Symfony Form behavior specifically, consider using symfony/form directly or a maintained Laravel form package rather than wrapping a Symfony bundle.
- What are the production risks of adding sbsedv/form-bundle to a Laravel app?
- Release risk is low because v1.10.0 is a constraint-only change, but architectural risk is high for Laravel-first teams. Widening one Symfony constraint can push Composer toward a Symfony 8 resolution that conflicts with other pinned dependencies. You also inherit a higher PHP baseline if Symfony 8 is selected, and the integration glue is unsupported upstream.
- How do I test sbsedv/form-bundle integration in a Laravel project?
- Test the hand-wired service provider by asserting that your form types and extensions resolve from the container and render expected fields. Add Composer constraint tests across your supported Symfony and PHP matrix, because the bundle's own CI may not exercise every combination. Include a smoke test for validation and rendering workflows, not just class existence.
- Is sbsedv/form-bundle actively maintained and safe to depend on?
- The v1.10.0 release is a single constraint-widening pull request that keeps pace with Symfony 8, which is a mild positive signal. The maintainer footprint is small, and a single-PR release cadence suggests limited test depth across the Symfony version matrix. Check tagged release history and CI coverage before treating it as a long-term dependency.
Weaver
How can I help you explore Laravel packages today?