-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Editor: Optimize 'PostAuthorCheck' component data selection #69105
Conversation
Size Change: +4 B (0%) Total Size: 1.84 MB
ℹ️ View Unchanged
|
Flaky tests detected in f8ba92a. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/13213851551
|
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 👍
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. |
Thanks for testing, @t-hamano! |
What?
PR updates the data selection logic in the
PostAuthorCheck
component and avoids querying users when the author can't be changed for a post type.An author can't be assigned to a post type when it doesn't support authors, or the current user doesn't have the right capabilities.
Why?
Reduces the number of network requests made when opening templates or template parts in the site editor.
Testing Instructions
Testing Instructions for Keyboard
Same.
Screenshots or screencast