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
Currently, when setting Flag states from django-admin it only shows the condition when flag is enabled but it is not trivial since flag can be both used for enabling and disabling a feature.
Can we make it in such a way that on one side it shows the condition when the flag is enabled and what is the value that is currently set.
Something like this:
PS: The condition is also somewhat misleading, since I want to disable the feature when it is False, but the condition always says enabled.
I hope this is making sense!!
The text was updated successfully, but these errors were encountered:
@ArcD7 That's not a bad idea — I'd like to do something more in the admin (wagtail-flags has a much richer view, but the Wagtail admin is somewhat easier to customizable and wagtail-flags is only useful if you're using Wagtail). As it is, the Django-Flags admin is very barebones.
One thing that may or may not be helpful for your immediate needs, Django-Flags has a Django Debug Toolbar panel that can describe flag conditions and state for the current request: https://cfpb.github.io/django-flags/debugging/
@willbarton Thanks for the reply, unfortunately I'm not using wagtail. Maybe I can fork the library and work on the Django-Flags admin. Any ideas for a good starting point?
Currently, when setting Flag states from django-admin it only shows the condition when flag is enabled but it is not trivial since flag can be both used for enabling and disabling a feature.
Can we make it in such a way that on one side it shows the condition when the flag is enabled and what is the value that is currently set.
Something like this:
PS: The condition is also somewhat misleading, since I want to disable the feature when it is False, but the condition always says enabled.
I hope this is making sense!!
The text was updated successfully, but these errors were encountered: