RTC: Clarify WPBlockSelection type and link to duplicates in other packages.#77862
RTC: Clarify WPBlockSelection type and link to duplicates in other packages.#77862
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 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. |
|
@alecgeatches or @maxschmeling would you be willing to review the docblock change and let me know if I’ve misunderstood anything, particularly the part about the intermediate selection states? |
19721df to
58ec519
Compare
|
@copilot there’s a do all of this EXCLUSIVELY in a new PR — DO NOT interact on this PR. it’s important to keep your exploratory work separate. |
|
Size Change: 0 B Total Size: 7.87 MB ℹ️ View Unchanged
|
d61e793 to
c67e682
Compare
…ckages. The `WPBlockSelection` type is more complicated than it may seem at face value. This change expands the docblock information on the type and links together the currently-existing duplicates in other packages, which are duplicated to avoid creating circular dependencies. This is prepartory work for #77658, but stands on its own as a clarifying update.
c67e682 to
11dd3f3
Compare
|
Flaky tests detected in 11dd3f3. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/25240965441
|
What
The
WPBlockSelectiontype is more complicated than it may seem at face value. This change expands the docblock information on the type and links together the currently-existing duplicates in other packages, which are duplicated to avoid creating circular dependencies.This is preparatory work for #77658, but stands on its own as a clarifying update.
Why?
The existing type information is sparse and ambiguous. The RTC copy of the type mentioned and “intermediate selection state” without indicating what that could mean.
Insightful docs lead to better understanding of the code for humans and bots.
How?
This is a comment-only change.
Use of AI Tools
An LLM was used to review the PR which introduced the type in the
core-datapackage, as well as the code that was changed, to investigate intermediate selection states.