-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Revise the rendering of feature state #52635
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
base: main
Are you sure you want to change the base?
Conversation
✅ Pull request preview available for checking
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
/approve
|
||
[feature_gate_enabled] | ||
other = "(enabled by default: {{ .enabled }})" | ||
other = "(enabled by default)" |
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.
Caution: this might break localizations that still rely on the old text.
If we're OK with that, we can proceed.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lmktfy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/area web-development |
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.
lgtm
This PR changes the logic for rendering feature state.
Currently, a feature state is rendered as "enabled by default: true" or "enabled by default: false". A more user-friendly way to render it should be "enabled by default" or "disabled by default". This saves users some brain cells when reading the feature state.