Storybook: Add stories for BlockAlignmentControl and BlockAlignmentToolbar components #67233
+126
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
akasunil
added
[Type] Developer Documentation
|
Size Change: 0 B Total Size: 1.84 MB ℹ️ View Unchanged
|
…-alignment-control-stories
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
t-hamano
reviewed
Dec 8, 2024
There was a problem hiding this comment.
Thanks for the PR!
While reviewing this PR, I noticed that the documentation for this component itself is insufficient. Not all props that are actually supported are documented.
Specifically, controls and isCollapsed. As for the isToolbar prop, it is determined internally depending on whether you use BlockAlignmentControl or BlockAlignmentToolbar, so there is no need to document it.
Could you investigate the behavior of these two and reflect it in the README and Storybook?
| argTypes: { | ||
| value: { | ||
| control: { type: null }, | ||
| defaultValue: 'undefined', |
There was a problem hiding this comment.
defaultValue is deprecated so let's remove it. It should not affect behavior.
| argTypes: { | ||
| value: { | ||
| control: { type: null }, | ||
| defaultValue: 'undefined', |
There was a problem hiding this comment.
defaultValue is deprecated so let's remove it. It should not affect behavior.
| */ | ||
| const meta = { | ||
| title: 'BlockEditor/BlockAlignmentToolbar', | ||
| component: BlockAlignmentToolbar, |
There was a problem hiding this comment.
Suggested change
| component: BlockAlignmentToolbar, | |
| component: BlockAlignmentToolbar, | |
| parameters: { | |
| docs: { canvas: { sourceState: 'shown' } }, | |
| }, |
Let's show the Source panel.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #67165
What?
This PR will add stories for
BlockAlignmentControlandBlockAlignmentToolbarcomponents in the StorybookWhy?
Most of Block Editor components don't have stories.
Testing Instructions
npm run storybook:devBlockAlignmentControlandBlockAlignmentControlstories.Screenshots or screencast
BlockEditor-BlockAlignmentControl---Docs-.-Storybook.webm