Storybook: Add stories for the TextDecorationControl component

[himanshupathak95]

Part of #67165

What?

This PR improves the Storybook stories for the TextDecorationControl component in the block editor. It includes stories demonstrating different text-decoration states.

Why?

As part of the ongoing effort to improve component documentation and testing (tracked in #22891), we need comprehensive stories for all Block Editor components.

Testing Instructions

• Start Storybook by running npm run storybook:dev
• Open Storybook at http://localhost:50240/
• Navigate to "BlockEditor/TextDecorationControl" in the Storybook sidebar
• Test the following stories:
  • Default (no decoration)
  • WithUnderline (underline decoration)
  • WithStrikethrough (strikethrough decoration)
  • WithCustomClass (custom class name)

Screencast

text-decoration-control-story.mov

[github-actions]

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: himanshupathak95 <[email protected]>
Co-authored-by: t-hamano <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[t-hamano]

Thanks for the PR!

I would like to make two suggestions.

• It looks like you are adding as many variations as possible as individual stories, but this seems redundant. All these props can be changed from the Controls panel. Also, if we go ahead with this approach, we will probably add similar variations to all other block editor components 😅
• It is certainly easier to understand with demo text, but Storybook is for testing and developing a single component itself. How this component interacts with the outside world is the responsibility of the developer who uses this component, and I think it is better not to include it in the story.

With that in mind, I think it would be best to focus on just the following two improvements for this PR. What do you think?

• Add the missing propsI (value, className) to argTypes
• Convert to CSF3 format (See this comment)

[himanshupathak95]

Thanks, @t-hamano for the suggestions.

I have addressed all the comments. Please let me if we can improve further.

Screen.Recording.2024-12-11.at.16.17.33.mov

[t-hamano]

Thanks for the PR! It looks almost good, but I'd like to give you some additional feedback 🙏

[himanshupathak95]

I have addressed all the comments. Thanks a lot, @t-hamano for the additional suggestion and for improving the overall structure of the story 🙌🏻

[t-hamano]

LGTM 👍