-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Query Loop: Check for postTypeFromContext before using it #66655
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
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. |
ellatrix
left a comment
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.
Perhaps at some point we should add some e2e tests.
|
Yes, e2e tests would be good! Happy to work on that as a follow-up. |
|
Size Change: +4 B (0%) Total Size: 1.81 MB
ℹ️ View Unchanged
|
…66655) Co-authored-by: mikachan <[email protected]> Co-authored-by: ellatrix <[email protected]>
What?
Fixes an issue introduced in #65820, where the Query Loop block gets stuck showing the loading spinner after being inserted.
Why?
It seems to be because we're trying to use
postTypeFromContextwhen it's undefined, so we should check that it exists before running logic against it.How?
Check for
postTypeFromContextbefore using it.Testing Instructions
Screenshots or screencast