You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.
When working with a growing number of switches eventually there will be a moment when you'd like to organise things a bit more.
Currently, one is presented with a list of switches in the admin interface. If you don't follow a nifty naming scheme it's hard to maintain overview and quickly find what you're looking for.
What if switches could be organised by something like app/feature/tags? A switch could have an optional field like feature. Question is how to make this conveniently browsable via /admin.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When working with a growing number of switches eventually there will be a moment when you'd like to organise things a bit more.
Currently, one is presented with a list of switches in the admin interface. If you don't follow a nifty naming scheme it's hard to maintain overview and quickly find what you're looking for.
What if switches could be organised by something like app/feature/tags? A switch could have an optional field like
feature
. Question is how to make this conveniently browsable via /admin.The text was updated successfully, but these errors were encountered: