-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Query and Search blocks: support for Instant Search via render_block_context
filter
#67013
Conversation
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @ktmn. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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. |
Size Change: +457 B (+0.03%) Total Size: 1.82 MB
ℹ️ View Unchanged
|
render_block_context
filter
Flaky tests detected in db5f965. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/12036199277
|
Closing in favor of #67181. There is nothing obviously wrong with this approach, but using the |
What?
An implementation of the instant search using the Query and Search blocks. Please see #63147 for a full description.
An alternative to #63147 and #67181.
Fixes #63053.
Why?
The approach in the current PR is more concise and reduces the repetitive code compared to #63147.
How?
Using
render_block_context
to inject the relevant search query into the context. See also this comment for more context.Testing Instructions and screencast
See #63147.