Weave Code
Wizard Annotation Bundle Laravel Package
ibrows/wizard-annotation-bundle
A Symfony bundle that brings annotation-driven wizard flows to your application. Declare multi-step form sequences in controller annotations, reducing boilerplate and keeping step logic organized, readable, and easy to maintain. Ideal for guided forms and checkout-style processes.
At a glance
Frequently asked questions about Wizard Annotation Bundle
- Can I use ibrows/wizard-annotation-bundle in a Laravel application?
- No. It is a Symfony bundle, not a Laravel package. It hooks Symfony's HTTP kernel and controller-resolution pipeline and reads Doctrine annotations, while Laravel has no analogous bundle registration, kernel event hook, or annotation-routing layer. There is no seam to plug it into a Laravel application.
- What does IbrowsWizardAnnotationBundle actually do?
- It provides annotation-driven wizard flows for Symfony applications, letting you declare multi-step form sequences in controller annotations. The useful pattern is declarative step methods, per-step validation hooks, and session-held wizard position. The bundle itself is a Symfony 2-era artifact, not a Laravel component.
- How do I install ibrows/wizard-annotation-bundle in Laravel?
- You should not install it in a Laravel app. Composer would pull Symfony 2-era components and a Doctrine annotation reader into your dependency graph, risking container, autoloading, and PHP-version conflicts with no functional payoff. Even in a Symfony estate it would need a rewrite rather than a drop-in install.
- Which Laravel versions and PHP versions are supported?
- There is no supported Laravel version. The package targets Symfony 2-era PHP and DI wiring, so its constraints are incompatible with current Laravel and PHP 8.x without patching. Modern PHP attributes have also superseded the annotations it relies on.
- How is the wizard configured in this bundle?
- Configuration is annotation-based: step methods are declared in controller annotations and discovered through Doctrine's annotation reader plus Symfony's controller resolution. Laravel's convention-over-configuration routing has no equivalent layer for this. If you want declarative steps in modern PHP, use attributes, but you still need to build the wizard state machine yourself.
- How should I test a multi-step wizard in Laravel if I rebuild this pattern?
- If you rebuild the pattern natively, test step ordering, per-step validation timing, back and forward navigation, resume-token persistence, and abandonment handling. Use Laravel feature and HTTP tests to exercise each transition and assert the state store after every step. The original bundle is not meaningfully testable inside a Laravel app because the Symfony kernel and annotation layer are absent.
- Is it safe to use this package in production?
- Do not use it in Laravel production. The technical risk is high and unmitigated: zero stars, zero dependents, single-vendor origin, no maintainer community, and no evident path for security patches. Abandonment risk is already realized, so treat it as a design reference rather than a dependency.
- What are the best Laravel alternatives for multi-step forms and wizard flows?
- For Laravel, build a native wizard controller or invokable step actions plus a small step registry, per-step FormRequests, and a session- or token-backed state store; roughly 200 to 400 lines gives you full ownership. If you prefer a vendor, evaluate maintained Laravel wizard or form-flow packages against your requirement list. In Symfony, use PHP attributes plus the Symfony Workflow component instead of resurrecting this bundle.
- Is the package maintained, and will it receive security fixes?
- No. The project is an artifact of the Symfony 2 era with no visible downstream validation or maintainer community. Doctrine annotations are in maintenance mode and PHP 8 attributes are the modern replacement. There is no credible path for bug fixes or CVE patches, so it should not be treated as a maintained dependency.
- Can I migrate from this Symfony bundle to Laravel?
- There is nothing to migrate if you are on Laravel because this bundle was never running there. The recommended path is harvest-and-reimplement: document step ordering, back-navigation, validation timing, and state persistence semantics, then rebuild them on Laravel primitives. In a Symfony estate, modernize to attributes and Symfony Workflow rather than porting the bundle as-is.
Weaver
How can I help you explore Laravel packages today?