-
Notifications
You must be signed in to change notification settings - Fork 1
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
refactor: upgrade storybook #93
Conversation
✅ Deploy Preview for storybook-ui-seeds ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
&[data-variant="highlight"] { | ||
background-color: var(--seeds-color-highlight); | ||
border-color: var(--seeds-color-highlight); | ||
&[data-variant="warn"] { |
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.
Updated the naming here to warn - we don't have a highlight in the Figma tokens, and the colors are the same (confirmed with design)
@@ -153,7 +154,8 @@ | |||
--seeds-bg-color-surface: var(--seeds-color-white); | |||
--seeds-bg-color-muted: var(--seeds-color-gray-100); | |||
--seeds-bg-color-disabled: var(--seeds-color-gray-450); | |||
--seeds-bg-color-inverse: var(--seeds-colors-gray-800); | |||
--seeds-bg-color-inverse: var(--seeds-color-gray-800); |
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.
Fixes a typo
@@ -1,39 +1,36 @@ | |||
:root { |
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.
I just organized this file and moved strings around
&[data-variant="in-process"] { | ||
background-color: var(--seeds-color-highlight-light); | ||
color: var(--seeds-color-highlight-darker); | ||
&[data-variant="warn"] { |
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.
Updated the naming here to warn - we don't have an in-process
in the Figma tokens, and the colors are the same (confirmed with design)
@emilyjablonski I've found a difference in the URLs between the old system and Storybook 8 for the documentation pages. OLD URL: NEW URL: This is only an issue with regards to the zeroheight docs embeds. We'd have to update all of them manually once this goes to prod. Or I wonder if there's a way to set up a redirect? |
@jaredcwhite Good call out! I was anticipating a followup to manually update the embeds 🫡 |
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.
Left some feedback for you. I'm glad we'll be on Storybook 8 now, looks really good!
<Meta of={stories} /> | ||
|
||
<Title /> | ||
<Subtitle>Button components are interactive elements that trigger an action when clicked.</Subtitle> |
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.
So…this looks really nice in the new Storybook theme, but it'll also show up in the Props embeds in zeroheight. I guess that's fine, but something to keep in mind so it's not too repetitive when viewing in zeroheight.
Post-merge, I will 1) Post the breaking changes in our consumers channel and 2) Update the Zeroheight Storybook embeds! |
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.
📚
🎉 This PR is included in version 1.18.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Upgrades Storybook to be able to support some of the documentation requests from SF.
This PR 1) Upgrades Storybook + documentation, and (2) introduces new shared types that are used across components instead of string unions (none of these are breaking changes, but having importable types has come up a few times as well).
Each code change unrelated to this has a comment on it. This includes two separate changes that are breaking, which is to rename the
highlight
variant of Button towarn
, and thein-process
variant of Tag towarn
, to match the tokens and designs. (UPDATE: Now also includes renaming instances of accent to highlight!)How Can This Be Tested/Reviewed?
The huge diff is mostly in the lock file.
Compare the old Storybook to the deploy preview here to see changes and ensure things are looking good! The Button and Tag stories will be the only ones w the naming adjustment to
warn
.There are now
Checklist: