flagception-bundle
flagception-bundle copied to clipboard
bestit
Feature flags on steroids!
```php /** * @Route("/blog/{page}", condition="service('flagception.manager.feature_manager').isActive('feature_123')") */ public function listAction($page) { // ... } ``` For Symfony 6.1 users, this feels a bit cleaner than setting a value in the routing...
```php #[Feature(name: "abc")] #[Route('/demo', name: 'app_demo')] public function demo(): Response { return $this->render('app/index.html.twig', [ 'controller_name' => 'Demo', ]); } ``` works now, as does using this at the controller class...
With [update](https://github.com/bestit/flagception-bundle/commit/c16e7b993d9082be593a542f8bf44c8cfb3aed3e) the default class for `flagception.activator.chain_activator` was set to `Flagception\Activator\ChainActivator` but within `src/Profiler/FeatureDataCollector.php` type was still only accepting `TraceableChainActivator`
The latest version of Symfony allows the routing condition to access a service, so developers can write: ```php #[Route('/demo', name: 'app_demo', condition: "service('flagception.manager.feature_manager').isActive('beta')")] public function demo(): Response { return $this->render('app/index.html.twig',...
All the cool kids are using attributes instead of annotations... I'll submit a PR in a bit, so we can do: ```php #[Feature(name: "abc")] #[Route('/demo', name: 'app_demo')] public function demo():...
After upgrading to version 4.3 which hides the `TraceableDataCollector` when `APP_DEBUG=0` (https://github.com/bestit/flagception-bundle/pull/89), I now get the following error when running tests with debug mode disabled: ``` TypeError: Flagception\Bundle\FlagceptionBundle\Profiler\FeatureDataCollector::__construct(): Argument #1...
Hello, We're running quite old Symfony 2.8.x based application. The symfony profiles shows "Features" section but not the configured features. However, I can actually work with them in the code....
Hi, We are use to manage our product features with your bundle. Normally we can check if a feature is available on php, twig and Javascript time. Our main problem...
The Environment activator does a lookup if a specific environment variable exists. It would be useful to allow a comparison for this environment value. Use case: I want to enable...
`TraceableChainActivator` extends `ChainActivator`, but it always uses `STRATEGY_FIRST_MATCH` strategy. I think the bundle should provide a configuration option to set the desired strategy and that `TraceableChainActivator` should honor it.
