-
-
Notifications
You must be signed in to change notification settings - Fork 736
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
🟢 feat: Dependent feature toggles #2255
Comments
+1 Was going to suggest that too! Currently we map our toggle dependencies in the code to offer a single |
+1 |
This issue is actively worked on starting this week. We'll be adding updates after major milestones. |
This change adds the `dependencies` property to the client feature struct, opening the path for dependent feature toggles: Unleash/unleash#2255
## Description This change adds the dependencies property to the client feature struct, opening the path for dependent feature toggles: Unleash/unleash#2255 ## Commits * feat: add `dependencies` property to client feature struct This change adds the `dependencies` property to the client feature struct, opening the path for dependent feature toggles: Unleash/unleash#2255 * Add tests for dependent features
This feature is implemented: https://docs.getunleash.io/reference/dependent-features with single parent dependencies for now |
Allow one toggle to depend on another toggle when evaluating if the toggle is enabled.
Should be possible to depend on multiple toggles:
We will not support multiple toggles in a chain
We will not support circular dependencies
Note
This will also require updates to ALL SDKs, so we should align on the protocol quite early.
The text was updated successfully, but these errors were encountered: