-
Notifications
You must be signed in to change notification settings - Fork 578
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 className back to TokenBase #5420
Conversation
🦋 Changeset detectedLatest commit: d02eca8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks! |
size-limit report 📦
|
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! Thanks 🙏🏼
* Add className back to TokenBase * Adding tests and fixing implementation * Create dirty-wasps-behave.md --------- Co-authored-by: Marie Lucca <40550942+francinelucca@users.noreply.github.com>
* Add className back to TokenBase * Adding tests and fixing implementation * Create dirty-wasps-behave.md --------- Co-authored-by: Marie Lucca <40550942+francinelucca@users.noreply.github.com>
Prior to #5271, the
className
inTokenBase
was part of the...rest
variables that were spread onto the token base. Now that theclassName
is directly referenced as part of the feature-flagged token, we need to directly reference it for the non-feature flagged token.Rollout strategy
Testing & Reviewing
Create a
Token
with a class name, that class should be on the resulting rendered token.Merge checklist