-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the limit of 3 keywords for the block registration #13848
Conversation
@gziolo why was this undocumented when it's still something that applies? Docs should be clear about it, no? Also, why the hard limit? Couldn't find anything about the reasoning behind this limitation. Asking just for curiosity, not sure I'd ever need more than three keywords when I can have more than one in each string. |
There is no limit anymore. |
But only the first three keywords are used when searching for a block. Am I missing something? |
Can you reproduce it? Looking at code, I can't find any logic which would ignore any keywords:
|
You're right. I've just tested with a couple blocks I built from scratch and it definitely shows up. Issue was with ACF blocks so it might be something on their side. I'll look into it and follow up there. Sorry for the trouble ❤️ |
It's totally fine. Thank you for testing with custom blocks 👍 |
Description
Opened to rebase and close #11953. All work was done by @jameelmoses.
Fixes: #11949
Instead of failing to register a block if more than 3 keywords are given, only return the first 3 by slicing the keywords array.
How has this been tested?
npm run lint
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: