Skip to content

Editor: Add excludeCurrent support to the Query Loop block.#12016

Open
t-hamano wants to merge 1 commit into
WordPress:trunkfrom
t-hamano:65373-exclude-current-post-from-query-block
Open

Editor: Add excludeCurrent support to the Query Loop block.#12016
t-hamano wants to merge 1 commit into
WordPress:trunkfrom
t-hamano:65373-exclude-current-post-from-query-block

Conversation

@t-hamano
Copy link
Copy Markdown
Contributor

Use of AI Tools

AI assistance: Yes
Tool(s): GitHub Copilot, ChatGPT
Model(s): GPT-5.1
Used for: Initial code skeleton and test suggestions; final implementation and tests were reviewed and edited by me.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

Allow the Query Loop block to exclude the current post from its results
by adding handling for the `excludeCurrent` query property directly in
`build_query_vars_from_query_block()`. When enabled, the current post ID
is merged into `post__not_in`. This brings the feature into core instead
of relying on the `query_loop_block_query_vars` filter.

Props from Gutenberg PR #64916.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@t-hamano t-hamano marked this pull request as ready for review May 30, 2026 12:54
@github-actions
Copy link
Copy Markdown

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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props wildworks.

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

@github-actions
Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant