-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Navigator: refactor Storybook code to TypeScript and controls #44979
Conversation
39e623c
to
d7b0103
Compare
argTypes: { | ||
as: { control: { type: null } }, | ||
children: { control: { type: null } }, | ||
initialPath: { control: { type: null } }, |
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 disabled the control for initialPath
because changing it doesn't make any difference (it's only used on the component's first render)
Size Change: 0 B Total Size: 1.27 MB ℹ️ View Unchanged
|
@@ -5,6 +5,7 @@ | |||
### Bug Fix | |||
|
|||
- `FontSizePicker`: Ensure that fluid font size presets appear correctly in the UI controls ([#44791](https://github.com/WordPress/gutenberg/pull/44791)). | |||
- `Navigator`: prevent partially hiding focus ring styles, by removing unnecessary overflow rules on `NavigatorScreen` ([#44973](https://github.com/WordPress/gutenberg/pull/44973)). |
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.
Adding a note for #44973 since it wasn't added in the original PR
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.
Nice work @ciampo 👍
All the changes and style tweaks make sense.
I didn't spot any unintended differences in Storybook between this PR and trunk. LGTM 🚢
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.
Nice and clean 🚀
What?
Part of #35744
Refactor
Navigator
's Storybook code to TypeScript and controls, thus enabling auto-generated documentation.Why?
Improving the code quality and the documentation of
@wordpress/components
.How?
Navigator
sub-components are named/exported internally (as suggested in the migration guide)cx
andcss
functions, in favour or simpler inline styles (this is to show that Emotion is not necessary to consume and style our components)Reviewing this PR commit-by-commit may ease the reviewing process.
Testing Instructions
Interact with
Navigator
's Storybook examples, make sure they look and work as ontrunk
.