- Is fintem/feature-toggle-bundle compatible with Laravel?
- No. It is packaged as a Symfony bundle with a bundle class, dependency-injection extension, and compiler pass, so it does not integrate with Laravel's service-provider and container model. For Laravel, treat it as a design reference and implement flags with config, cache, a Feature facade, or Laravel Pennant. Do not add it as a Composer dependency in a Laravel application.
- How do I install fintem/feature-toggle-bundle?
- It is installed via Composer as fintem/feature-toggle-bundle and registered as a Symfony bundle. You must confirm its composer.json PHP and Symfony constraints before attempting installation, because the last release was 2018 and targets Symfony 3.x/4.0 and PHP 7.1/7.2. On modern PHP 8.x or current Symfony versions it will likely fail dependency resolution or require unsafe --ignore-platform-reqs workarounds.
- Does fintem/feature-toggle-bundle support PHP 8 and Symfony 6?
- No verified support exists. The last release is dated 2018-09-04, which places it in the Symfony 3.x/4.0 and PHP 7.1/7.2 era. PHP 8 incompatibilities are likely from curly-brace string offsets, dynamic properties, and reflection deprecations, and the Composer constraints will likely block Symfony 5/6 upgrades. Budget for compatibility shims and constraint widening if you fork it.
- How are feature flags evaluated in fintem/feature-toggle-bundle?
- The exact mechanism needs verification from the source: it may use annotation-driven toggles on controllers or services, config-declared flags, or a storage-backed variant. The overview describes declarative toggle configuration, runtime checks per user, environment, or custom strategy, and extension points for activation rules. Before adopting, confirm whether evaluation uses annotations and reflection, compiled config, or a database table, because that determines both performance and migration difficulty.
- Does fintem/feature-toggle-bundle support percentage rollouts and user targeting?
- The overview claims runtime checks per user, environment, or custom strategy, and mentions gradual rollouts and A/B experiments, so percentage rollout and targeting may be possible through custom activation rules. However, the exact feature set is unverified, and the package may be boolean-only or require custom strategy code. Confirm audit trail and tenant targeting support before relying on it.
- Is fintem/feature-toggle-bundle safe for production use?
- Treat it as high risk. It has three stars, zero dependents, a composite score of 0.145, and no release since 2018, which means no production evidence, no downstream compatibility pressure, and no security response path. The vendor is a single small publisher with no visible community or governance. For production, vendor a patched fork behind your own interface or reimplement the concept natively.
- What is the license for fintem/feature-toggle-bundle?
- The license is ambiguous in the provided material and must be confirmed before any vendoring, forking, or redistribution inside your estate. Check the repository LICENSE file and composer.json license field directly. If you need an internal fork, confirm that the license permits modification and internal redistribution. Do not assume MIT or any permissive license without verification.
- What alternatives should I use for feature flags in Laravel?
- For Laravel, use Laravel Pennant if your framework version supports it, or build a small native Feature facade backed by config and cache. You can also define your own FeatureFlag interface with isEnabled(string $flag, ?Context $ctx): bool and put targeting logic behind it. If you need a Symfony bundle specifically, look for a maintained flag bundle rather than a 2018 artifact, and verify PHP 8 and current Symfony support.
- How do I test feature toggles if I fork fintem/feature-toggle-bundle?
- Wrap the bundle behind your own FeatureFlag interface and test that interface with deterministic contexts, not the bundle internals. Add a test suite because the original package almost certainly lacks PHP 8 coverage and a modern Symfony test matrix. Cover default behavior for undefined or unevaluable flags, percentage rollout boundaries, and user or tenant targeting. Then you can replace the fork with a native implementation in one file.
- Is fintem/feature-toggle-bundle maintained, and is there a maintained fork?
- It appears unmaintained since 2018, with roughly seven years without a release and no visible community, CLA, or governance. No maintained fork or successor is identified in the provided assessment, and vendor reachability is unknown. Check Packagist, GitHub issues, and the vendor's status before investing. If no fork exists, preserve the concept rather than the code.