-
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
Pattern Transformations Menu: do not use Composite store #65040
Pattern Transformations Menu: do not use Composite store #65040
Conversation
Size Change: -21 B (0%) Total Size: 1.78 MB
ℹ️ View Unchanged
|
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - works the same as in trunk 👍
I did spot something that feels off though (it's the same in trunk
, so this PR can be merged):
- Insert a "Query Loop" block
- Click the transform button
- Use the keyboard to navigate to "Patterns" (arrow up/down for up/down, space to select)
- Verify arrow up/down works for changing the selected pattern.
- Try shift+tab or esc, but you won't be able to get away of that view or go back to the transform menu. This feels off.
Yeah, I think that's because that piece of UI is not actually using a It should get better once we refactor it to |
What?
Extracted from #64723
Do not use Composite's store directly in Pattern Transformations Menu
Why?
See #63704 (comment)
How?
We recently made changes so that:
Composite
component accepts the same props asuseCompositeStore
;Composite
subcomponents already receive the correctstore
without need for the consumer to pass it explicitlyTherefore, we can migrate from
to
Testing Instructions
trunk
— ie. it is one tab stop, and using arrow keys moves the focus on the other list itemsScreenshots or screencast
Kapture.2024-09-04.at.11.45.00.mp4