Gutenberg_REST_Posts_Controller_6_7: Support exact search in the REST API posts endpoint. #66070
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.
What?
Introduces the changes from https://core.trac.wordpress.org/changeset/59034/ to Gutenberg_REST_Posts_Controller_6_7
fixes #66069
Why?
WordPress 6.7 is going to add support for the
exactsearch_semanticsto the REST API posts controller ( see https://core.trac.wordpress.org/changeset/59034/ ) and since the Gutenberg 19.4.0 is overriding related controller (Gutenberg_REST_Posts_Controller_6_7) it's necessary to port the logic in order to preserve the new feature when Gutenberg is run on WordPress 6.7How?
Ports the logic introduced to WordPress in the https://core.trac.wordpress.org/changeset/59034/
Testing Instructions
Create posts similar to the ones in related PHPUnit tests ( see https://core.trac.wordpress.org/changeset/59034/ ) and perform search via the REST API endpoints (again, similarly to what the WordPress PHPUnit tests do)