Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: enableAll and disableAll overrides fallback #243

Conversation

chriswk
Copy link
Contributor

@chriswk chriswk commented May 8, 2024

As discussed in #239 - When all is enabled, we had a bit of a surprising
behaviour where we'd fallback to fallback action for
isEnabled(featureName, fallback) even if all was enabled and feature
did not exist.

This PR fixes that, and adds tests to confirm this behaviour is intentional.

closes: #239

As discussed in #239 - When all is enabled, we had a bit of a surprising
behaviour where we'd fallback to fallback action for
`isEnabled(featureName, fallback)` even if all was enabled and feature
did not exist.

This PR fixes that, and adds tests to confirm this behaviour is
intentional.

closes: #239
@chriswk chriswk force-pushed the 239-fakeunleash-doesnt-take-into-account-global-activationdeactivation-for-certain-isenabled-method branch from 913d7b5 to e4d1e52 Compare May 8, 2024 13:44
@chriswk chriswk merged commit 132a086 into main May 14, 2024
4 checks passed
@chriswk chriswk deleted the 239-fakeunleash-doesnt-take-into-account-global-activationdeactivation-for-certain-isenabled-method branch May 14, 2024 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

FakeUnleash doesn't take into account global activation/deactivation for certain isEnabled method
2 participants