-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
docs(featureflags): define naming convention, unify existing flag names #15964
docs(featureflags): define naming convention, unify existing flag names #15964
Conversation
✅ Deploy Preview for v11-carbon-react ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for v11-carbon-react ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@kennylam @janhassel @lee-chase @matthewgallo @elycheea I would love your input here if you have any thoughts |
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.
Great write-up! Overall I think this makes a lot of sense and is a great way forward. Just left two thoughts.
Additionally, I think it might be good to first tackle and finalize #15966 before this to avoid confusion over that aspect with the tree view flag (consistent deprecation warning, extracting the logic you added to the TreeView
component to the useFeatureFlag
hook).
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.
yayyy 😎 looks so good!
…ature-flag-naming-convention
@alisonjoseph @janhassel this is updated and ready for a re-review |
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.
Looks great!
7d3d800
…es (carbon-design-system#15964) * docs(featureflags): define naming convention, unify existing flag names * docs(featureflags): rephrase content
Closes #15728
This PR proposes a naming convention for feature flags and outlines an approach for how to utilize them with breaking changes in major version releases.
Changelog
New
enable-experimental-treeview-controllable
as a replacement forenable-treeview-controllable
(which didn't follow the naming convention)Changed
Removed
enable-v11-release
flag from storybook docs, it's not used anywhere in the codebaseTesting / Reviewing
This spins off some new work that we'll need to tackle: