Type-hint contract instead of concrete class to allow switching features #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes In Code
When we fake a feature via the
Features::fake
method, the manager instance is swapped withFeatureFake
.Calling
fake
more than once will result in the following error:This happens because
FeatureFake
type-hints at aManager
instance but afterFeatures::fake
has been called for the first time, the facade root will return an instance ofFeatureFake
instead.To fix that, I changed the type expected for the
$manager
property to theFeatures
contract.Issue ticket number / Business Case
Switching a feature state can be useful in tests.
In my specific case, I noticed the issue when I faked a feature in a test
setUp
but had one specific test case where the feature had to be switched, resulting in the error.Checklist before requesting a review
the feature flags documentation repo.
enhancement
label for a new feature.