Patterns: provide a way to opt-out of Gutenberg patterns and core patterns updates #31924
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is a proof of concept (POC) to test a feature proposal.
This PR provides filters to opt out of:
See the issue for more context: #31922
How has this been tested?
By default all Gutenberg patterns should be available in the inserter.
To test the filters add the following block to the end of lib/init.php
Returning
false
fromshould_register_gutenberg_patterns()
should remove Gutenberg patterns.Returning
false
fromshould_update_core_patterns()
should not replace/update core patternsTypes of changes
Non-breaking additional functionality.
Checklist:
*.native.js
files for terms that need renaming or removal).