Form blocks: Update block categories for form, form-input, form-submission-notification, and form-submit-button#61916
Conversation
…ation, and form-submit-button
|
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. |
|
Sorry for the late reply, @amitraj2203. Could you rebase this PR o top or the trunk branch to move this forward? Personally, I feel the "Widgets" category is appropriate because the Search block, which is also an interactive block, is categorized under widgets. What do you think? Let's also get some other opinions. |
|
Using the "widgets" category seems like a good idea 👍 |
|
I've pushed an additional commit to change the category from |
…ssion-notification, and form-submit-button (#61916) * Update block categories for form, form-input, form-submission-notification, and form-submit-button * Form blocks: move from Design to Widgets category --------- Co-authored-by: amitraj2203 <amitraj2203@git.wordpress.org> Co-authored-by: t-hamano <wildworks@git.wordpress.org> Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: colorful-tones <colorful-tones@git.wordpress.org> Co-authored-by: carolinan <poena@git.wordpress.org> Co-authored-by: simison <87168+simison@users.noreply.github.com>
What?
Fixes: #60929
Why?
The form blocks: form, form-input, form-submission-notification, and form-submit-button uses the category
commonwhich is not a valid category inblock.jsonHow?
This PR updates the category for these blocks to
design