Weave Code
Form Bundle Laravel Package
elasticms/form-bundle
Generate dynamic forms from ElasticMS content configuration. This bundle builds forms out of your content types, keeping field definitions and structure in sync with your ElasticMS content model while rendering them in your Symfony application. Part of the elasticMS mono repository.
Generate forms based on elasticms configurations
Frequently asked questions about Form Bundle
- Can I use elasticms/form-bundle with Laravel 10 or 11?
- Not as a drop-in Laravel package. It is a Symfony bundle that generates forms from ElasticMS content configuration and depends on Symfony Form, Validator, Intl, Twig, and the Symfony DI container. A Laravel integration would need a container bridge and custom rendering, or a separate Symfony service called over HTTP.
- What is elasticms/form-bundle used for?
- It builds Symfony forms directly from ElasticMS content types so fields, labels, validation, and structure stay aligned with your content model. It is intended for Symfony applications already using ElasticMS, not as a general-purpose form builder. The transferable value is the schema-driven form pattern, especially for CMS-editable forms such as landing pages, onboarding, and questionnaires.
- How do I install elasticms/form-bundle?
- Install it with Composer as elasticms/form-bundle, but treat that as the final step. You first need a running ElasticMS instance, content types modeled for forms, and a Symfony app with the Form, Validator, Intl, Twig, and DI dependencies. The README is minimal, so verify requirements in composer.json and the elasticMS mono-repo documentation before planning.
- Do I need an ElasticMS instance to use this bundle?
- Yes. The bundle's value proposition is coupling form definitions to ElasticMS content configuration, so ElasticMS is effectively the schema store for your forms. That means a second system to deploy, secure, back up, and version, plus credentials and a network path from your application. Estimate that infrastructure work before estimating PHP integration work.
- Which Symfony versions does elasticms/form-bundle support?
- Release history shows two parallel maintained lines, 6.9.x and 7.x, with frequent patch churn. Mapping those lines to specific Symfony versions is not documented in the README; check composer.json and the mono-repo docs. Do not assume the latest tag matches your Symfony version.
- Is elasticms/form-bundle compatible with Laravel validation, FormRequest, and Blade?
- No, not natively. It relies on Symfony Form, Symfony Validator, and Twig-oriented rendering, while Laravel uses FormRequest, the Validator facade, and Blade. Bridging them means either running Symfony components inside Laravel with a container shim and reimplementing rendering, or isolating the bundle in a Symfony service and calling it over HTTP.
- How should I test forms built with elasticms/form-bundle?
- Test it in a Symfony context rather than with Laravel's testing helpers. Unit-test custom form types and validation constraints, then add functional tests that load real ElasticMS content types and submit representative payloads. If you run it as a separate service, test the HTTP boundary and error handling instead of driving Symfony internals from Laravel.
- What are the production risks and licensing concerns of elasticms/form-bundle?
- The main production risks are architectural: you must operate ElasticMS as a second system, and the bundle is tightly coupled to Symfony Form and Twig assumptions. Documentation is a stub with no code samples or upgrade notes, so unknown unknowns widen estimates. The license is LGPL-3.0, which is usually fine as an unmodified dependency but carries relink and notice obligations, so involve legal early.
- Is elasticms/form-bundle actively maintained?
- The repo is a read-only mirror of the elasticMS mono-repo, so issues and pull requests are routed there, and low stars or dependents on the mirror are misleading. Release history shows two maintained lines, 6.9.x and 7.x, with frequent patch churn. Evaluate the parent elasticMS project and its documentation rather than scoring this mirror alone.
- What alternatives should a Laravel team consider for dynamic forms?
- For Laravel teams, evaluate Laravel-native form builders, Livewire or Inertia-driven forms, Filament or Nova-style admin form builders, and custom schema-driven form services before adopting this bundle. If you need CMS-editable forms, elasticms/form-bundle is useful as a reference architecture for the pattern. It is rarely the right direct dependency for a Laravel-first codebase.
Weaver
How can I help you explore Laravel packages today?