Components: mark CustomSelectControl hint option as experimental#35673
Components: mark CustomSelectControl hint option as experimental#35673
CustomSelectControl hint option as experimental#35673Conversation
ntsekouras
left a comment
There was a problem hiding this comment.
Thanks for the follow up Marco! I was wondering if we should make this experimental for now.. We could revisit when the typescript/css-in-js is handled for this component.
What do you think?
Usually marking a component as experimental means:
In general, it's good practice to mark all components as experimental when they first get added to the codebase. Doing the second part means renaming all the imports using it — which we can do in Gutenberg, but will break every other codebase using this component (do we have any insights?) |
|
Oh no... I meant making(prefixing) the new property experimental, not the component. Sorry for the confusion I caused 😄 |
Ah I see! Do you mean something like |
Exactly! |
CustomSelectControl changesCustomSelectControl hint option as experimental
Hey @ntsekouras , I renamed the prop as suggested, based the changes made in #35395. Could you give it another round of review and make sure that I haven't missed any place when renaming the prop? Thank you! |
|
Size Change: +13 B (0%) Total Size: 1.07 MB
ℹ️ View Unchanged
|
ntsekouras
left a comment
There was a problem hiding this comment.
Looks great - thank you! 🚀
Description
Rename the
hintproperty for theCustomSelectControloptions introduced in #35395 to__experimentalHint, add CHANGELOG entryHow has this been tested?
Typography panel still works
Types of changes
Documentation
Checklist:
*.native.jsfiles for terms that need renaming or removal).