-
-
Notifications
You must be signed in to change notification settings - Fork 750
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
Allow to collapse strategy #9529
Comments
Hi, |
Thanks for getting back. Like I mentioned above, we have some flags where we have 30 strategies. Some of those strategies only apply to users, say, who installed the app between Jan 1 - Mar 31, 2024. We still want to keep this strategy active because we are aging the user. So now we have so many such strategies for a flag. So out of these 30 strategies, 80% are something that I don't want to look at every time I open the flag details page. I only care about the last 5-6 strategies that I would have added recently. So in such cases it would be helpful to be able to collapse some strategies so that I can focus on what's important to me in the moment. |
I see, thanks for sharing your need! I'll bring it back to the team and evaluate the need. Hide/show should be possible to include in some way :) |
Describe the feature request
I would like the ability to collapse strategy in the UI. Additionally the ability to "Collapse all" and "Expand all".
Happy to also contribute if the feature request gets approved
Background
We tend to have several strategies for a feature flag. The highest I have seen is 29 for an experiment flag. But there are several other flags where we have somewhere between 10-15 strategies. This might be largely related to how my company operates and how we run AB tests (where we need to keep old strategies to allow the users to age).
Solution suggestions
Not something to be done for v1, but for v2 we can also consider storing the collapse state for the user in localStorage. So that the next time they open the flag, the collapse state for each strategy can be restored.
The text was updated successfully, but these errors were encountered: