Expose ValidatedInputControl via privateAPIs#71451
Expose ValidatedInputControl via privateAPIs#71451m1r0 wants to merge 3 commits intoWordPress:trunkfrom
ValidatedInputControl via privateAPIs#71451Conversation
|
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. |
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @m1r0! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
|
@mirka @oandregal Because you have context, can you give it a quick look? |
|
Looks like this was implemented in #71514. Closing... |
What?
Related to this discussion, this PR exposes the
ValidatedInputControlcomponent via the privateAPIs.Why?
The
ValidatedInputControlcomponent has a suffix, which is something we need on a few forms on Calypso.