-
Notifications
You must be signed in to change notification settings - Fork 3
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
Fixed bug in notice-background-color-default #17
Conversation
READING spectrum-tokens:
TEST COMPLETE |
This warning is triggering because these two tokens have their constant-token-duplicate value set to true (their values are expected to be identical), but with this change their values are no longer the same so they need to be unique token entries in spectrum-tokens. I'm not sure what we do with uuids in this situation, @GarthDB. Do we deprecate the existing token definition with the current uuid, and create new ones for the separate light/dark values? Or something else? |
@GarthDB @mrcjhicks I think, we talked about using the uuid for light and generate new uuids for the other themes, in case these kind of changes happens. slack disc..
After merge, the sync script would apply the changes to spectrum-tokens and split up the constant token there as well. |
@karstens Thanks for the clarification; I'll make the changes to the diff script to resolve this type of an issue using the workflow you described. |
READING spectrum-tokens:
STUDIO SYNC SUMMARY
SPECTRUM SYNC SUMMARY
TEST COMPLETE |
READING spectrum-tokens:
STUDIO SYNC SUMMARY
SPECTRUM SYNC SUMMARY
SYNC COMPLETE |
Description
Fixed bug in the light theme value for
notice-background-color-default
, fromnotice-color-800
tonotice-color-600
Motivation and context
While updating the badge component in Figma, we noticed a bug where
notice-background-color-default
in S2 was entered incorrectly for light theme, and should instead match the value for S1Related issue
N/A – no Jira ticket for this patch
Types of changes
Checklist: