Epic: pheature-flags/pheature-flags#309

We need to update the FeatureRepository::remove contract to accept Feature instead of FeatureId:

public function remove(Feature $feature): void

Epic: pheature-flags/pheature-flags#297
Depends on: #15

We want to save Pheature\Core\Toggle\Write\Event\FeatureWasDisabled event on the Pheature\Core\Toggle\Write\Feature class when the feature is disabled.

Epic: pheature-flags/pheature-flags#297
Depends on: #15

We want to save Pheature\Core\Toggle\Write\Event\FeatureWasRemoved event on the Pheature\Core\Toggle\Write\Featureclass when theFeature` needs to be removed.

It's a work in progress but the first iteration is the creation of a new method Feature::remove that should save the event.

Epic: pheature-flags/pheature-flags#297
Depends on: #15

We want to save Pheature\Core\Toggle\Write\Event\FeatureWasEnabled event on the Pheature\Core\Toggle\Write\Feature class when the feature is enabled.

Epic: pheature-flags/pheature-flags#294

With the current implementation, we are emerging the result of every finder using array merge, this can cause duplicate results when the same toggle id is present in different finders, doing an array_replace_recursive instead of array merge will solve this issue.

Epic: pheature-flags/pheature-flags#297
Depends on: #15

We want to save Pheature\Core\Toggle\Write\Event\AnStrategyWasRemoved event on the Pheature\Core\Toggle\Write\Feature class when the strategy is removed from the feature.

Now we only test code with PHP 7.4, we will test at least with both 7.4 and 8 versions.

Epic: pheature-flags/pheature-flags#321

Add support for PHP 8.1 in composer.json and test for possible incompatibilities.

Epic: pheature-flags/pheature-flags#297
Depends on: #15

We want to save Pheature\Core\Toggle\Write\Event\AnStrategyWasAdded event on the Pheature\Core\Toggle\Write\Feature class when a strategy is added.

Epic: pheature-flags/pheature-flags#297

We have to store the actions that occurred in the Pheature\Core\Toggle\Write\Feature as events.

Example implementation, of what we are thinking on:

<?php
...
class Feature {
   private array $events = [];

   public function popEvents()
   {
       $events = $this-events;
       foreach($events as $event) {
            $this->apply($event); // not mandatory because we are not doing event sourcing here
       }
       $this->events = [];
       return $events;
   }
}

Epic: pheature-flags/pheature-flags#297
Depends on: #15

We want to save Pheature\Core\Toggle\Write\Event\FeatureWasCreated event on the Pheature\Core\Toggle\Write\Feature creation.

Epic: pheature-flags/pheature-flags#299 [toggle-core] Update issue template for bugs using new issue form in a YAML

In order to make easier the creation of bugs following a specific format, we should update the markdown file into a YAML file.

See Github Docs.

Using Psalm types for arrays will give us extra stability by adding strict array typing checks statically.

Epic: pheature-flags/pheature-flags#294

We have to add the ChainFeatureRepository responsible for the management of a feature by its identifier calling on each FeatureRepository injected through the constructor.

Epic: pheature-flags/pheature-flags#294

We have to add the ChainFeatureFinder responsible for the retrievement of a feature by its identifier calling on each FeatureFinder injected through the constructor.

It should do the following:

• It'll have injected an array of FeatureFinder elements.
• It should call every finder of the array.
• if the finder returns the feature, it'll return it.
• if the finder return no results, it'll call to the next finder.