Weave Code
Toggle Bundle Laravel Package
qandidate/toggle-bundle
Symfony bundle for Qandidate Toggle that brings feature flags into your app. Define toggles in configuration, check them via the toggle manager, and safely enable or disable features per environment or user without redeploying. Useful for gradual rollouts and A/B tests.
Qandidate ToggleBundle integrates the qandidate/toggle feature-flag library into Symfony, enabling runtime feature control without redeployments. Define toggles in configuration and check their state from application services, controllers, or templates.
- Declarative toggle configuration through Symfony config
- Built-in operators and conditions for targeted and gradual rollouts
- Container integration for injecting and evaluating toggles
- Twig support for conditionally rendering features
- Compatible with the standalone qandidate/toggle library
Frequently asked questions about Toggle Bundle
- Can I install qandidate/toggle-bundle in a Laravel application?
- No. qandidate/toggle-bundle is a Symfony bundle that relies on Symfony bundle registration, DI compiler passes, and a TreeBuilder configuration schema, none of which exist in Laravel. Installing it as-is will not work; the framework-agnostic qandidate/toggle core library can be ported behind a Laravel service provider instead.
- Does qandidate/toggle-bundle support Laravel 10 or Laravel 11?
- There is no Laravel support in this package. It is built for Symfony, and its Composer constraints likely target older Symfony and PHP versions, so it will not resolve against Laravel 10 or 11 without ignoring platform requirements. Treat it as a Symfony-only dependency.
- What is the difference between qandidate/toggle-bundle and Laravel Pennant?
- Laravel Pennant is the first-party feature flag package for Laravel, while qandidate/toggle-bundle is a Symfony bundle wrapping the Qandidate Toggle library. Pennant is maintained by the Laravel team and integrates natively with Laravel's container, facades, and Blade; the Qandidate bundle offers no Laravel integration. For new Laravel work, Pennant is the lower-cost, better-supported option.
- How do I integrate Qandidate Toggle feature flags into a Laravel app?
- Depend on the framework-agnostic qandidate/toggle core library rather than the Symfony bundle, then write a service provider that binds the toggle operator as a singleton and hydrates toggles from config/features.php. Expose a facade and a Blade directive for ergonomic checks. This is roughly 150–300 lines of glue code and keeps the toggle semantics without Symfony machinery.
- Is qandidate/toggle-bundle abandoned or safe for production?
- The project shows strong abandonment signals: only 89 GitHub stars, zero dependents, and a dormant upstream organization. You should assume no security fixes, no PHP 8 or modern Symfony catch-up, and no maintenance. It is not a safe production dependency for a new Laravel application.
- What PHP and Symfony versions does qandidate/toggle-bundle require?
- Bundles of this vintage typically pin Symfony 2.x or 3.x and PHP 5.6 or 7.x constraints, though the exact composer.json should be verified directly. Those constraints will usually fail to resolve against modern PHP 8.x, Symfony 5+, or Laravel 10+. Check Composer resolution before considering any integration.
- Can I use annotation-based feature toggles in Laravel like this bundle supports?
- The annotation support in qandidate/toggle-bundle is implemented through Symfony's annotation reader and DI wiring, so it does not carry over to Laravel. In Laravel you would typically use middleware, a facade, or Blade directives instead. Porting the concept is possible but requires reimplementation rather than reuse.
- How do I define feature toggles in a config file for Laravel?
- The bundle's config-file-driven toggle definitions can serve as a schema reference, but in Laravel you would create config/features.php and hydrate the Qandidate Toggle operator from it in a service provider. Be aware that config-file toggles are deploy-time: flipping a flag requires a deploy unless you wire in a mutable storage adapter. Runtime targeting needs a mutable store.
- What are good alternatives to qandidate/toggle-bundle for feature flags in Laravel?
- Laravel Pennant is the first-party choice and covers most use cases. For cross-language or hosted feature management, consider Unleash SDKs or OpenFeature-compatible providers. These are maintained and integrate cleanly with Laravel, unlike the Qandidate Symfony bundle.
- What should happen when a feature toggle source is unavailable in production?
- You must explicitly choose fail-open (serve the new path) or fail-closed (serve the old path), because toggle evaluation sits in request paths and failure behavior is a product decision. Document the policy per toggle and test it. Do not let an unavailable toggle source cause unhandled exceptions.
Weaver
How can I help you explore Laravel packages today?