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: im3dabasia <im3dabasia1@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>

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

Hi @t-hamano ,

When you have a moment please review my PR

Thanks @t-hamano for the feedback

I agree that adding stories for the other two components makes this much more complete.

I have now added the stories for __experimentalColorGradientSettingsDropdown and __experimentalPanelColorGradientSettings

There is some redundant code in the new stories, especially since both of these components are essentially wrappers around __experimentalColorGradientControl. Because they share many of the same props, I think there’s an opportunity to extract and reuse parts of the code—like the meta object, onChange handlers, and even Default.args.

Do you think it would be a good idea to generalize and share those parts across the three stories? Or would you prefer keeping things simple and explicit for ease of readability and understanding?

Looking forward to your thoughts!