-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Add feature flags to flutter doctor -v
#171307
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
Add feature flags to flutter doctor -v
#171307
Conversation
|
Example output: |
| } | ||
| // Add feature flags that are either enabled, or disabled compared to the default setting. | ||
| final List<String> featureFlags = <String>[ | ||
| ..._featureFlags.allConfigurableFeatures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider replacing splatting + list literal with a .toList() as that's shorter and less indented. I don't feel strongly about this, feel free to skip
| /// | ||
| /// [Feature.configSetting] is not `null`. | ||
| Iterable<Feature> get allConfigurableFeatures { | ||
| return allFeatures.where((Feature feature) => feature.configSetting != null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we include features that have a environmentOverride?
I don't know why someone would do this, but one could create a feature that has an environmentOverride but not a configSetting.
loic-sharma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Towards #38901.