Remove patterns from the Quick Inserter to prevent misuse in block-specific contexts

[rohitmathur-7]

What?

• Removing patterns from the Quick Inserter.
• Fixes Issue: Remove patterns from the Quick Inserter to prevent misuse in block-specific contexts #67693

Why?

• We are removing Patterns from the quick inserter to prevent misuse in block-specific contexts.

How?

• Set maxBlockPatterns to 0 which will help in not showing patterns in the quick inserter.

Testing Instructions

• Open the block editor and add any block (e.g., Social Links).
• Click the “+” button in the block toolbar to open the Quick Inserter.
• Search for items, and observe that patterns are not included in the results.

[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: rohitmathur-7 <[email protected]>
Co-authored-by: talldan <[email protected]>
Co-authored-by: richtabor <[email protected]>

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

[talldan]

@rohitmathur-7 Thanks for working on this. This will be a really great change to get merged.

In testing I still see at least one issue to resolve.

The + appender button tooltip still says 'Add pattern' instead of 'Add block':

I think you can probably go through the code a bit more and remove instances of prioritizePatterns and related code, as that seems to be what causes the issue.

[rohitmathur-7]

@rohitmathur-7 Thanks for working on this. This will be a really great change to get merged.

In testing I still see at least one issue to resolve.

The + appender button tooltip still says 'Add pattern' instead of 'Add block':

I think you can probably go through the code a bit more and remove instances of prioritizePatterns and related code, as that seems to be what causes the issue.

Sure @talldan ,
Apologies for the delayed response 🙇‍♂️, and thank you so much for reviewing the code.
I’ll work on the suggested changes today. 🚀

[rohitmathur-7]

Hii @talldan ,
I have updated the code to remove prioritizePatterns instances from wherever possible.
Can you please review the code again? 🙇
Thanks!

[talldan]

Thanks for updating the PR, @rohitmathur-7 .

This testing well, I'll approve and merge the PR.

[talldan]

Fixes Issue: #67693

@rohitmathur-7 A useful feature in github is that if you write this in a particular shorthand in the PR description, like 'Fixes #67693' , then github will automatically link the PR to the issue, and when the PR is merged the issue gets closed automatically.

You can see an example on #67838, if you hover your mouse over word 'Fixes' then there's a little tooltip. It also works with some other words like 'Closes'.

[rohitmathur-7]

Hi @talldan,
Thank you so much for reviewing, testing, and merging the PR! 🙇‍♂️🚀
I also appreciate the suggestion and will keep it in mind for future PRs. 😄