-
Notifications
You must be signed in to change notification settings - Fork 706
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
Features endpoint does not show disabled named feature #640
Comments
the named feature doesn't match to a bean so there is nothing to check. |
@spencergibb here is the use case example I'm thinking of:
Then the features endpoint would return "Feature 1" in disabled features if Let me know if this is not the intended use case of features endpoint. |
They should be in a single class that is conditional on property or share the same conditional |
Sorry, my previous comment was wrong. If they share the same conditional, then when that's disabled, "Feature 1" won't be displayed as "disabled" as there is no bean for the named feature as well. If not share the same conditional, then "Feature 1" is always in the enabled list. I'd like to get the list of all enabled and disabled features in that endpoint. Currently, for named features, it can only exist in the enabled list or not in the features endpoint at all, it will never exist in the disabled list. |
I can't think of a way to do it with named features. |
Here is what I'm thinking:
cc @twicksell any thoughts? |
For abstract feature, it checks whether there is a bean for that type or not, however, for named feature, it always adds to enabled features, instead of adding to disabled feature when there is no bean of the specified type (due to @ConditionalOn...)
The text was updated successfully, but these errors were encountered: