-
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
Fix failing PHPUnit tests #45265
Fix failing PHPUnit tests #45265
Conversation
Thanks @Mamaduka, looks like a great solution (that didn't occur to me). I'll quickly test locally to verify that it really falls back to |
Co-authored-by: Bernie Reiter <ockham@raz.or.at>
@ockham, I got inspiration from your comment for this fix 😄 |
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! Thank you for fixing 😊
@priethor @juanmaguitar This should also be included in GB 14.4 please 😊 |
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.
Thank you @Mamaduka 😍
I just cherry-picked this PR to the wp/6.1 branch to get it included in the next release: 739b2b0 |
Co-authored-by: Bernie Reiter <ockham@raz.or.at>
Co-authored-by: Bernie Reiter <ockham@raz.or.at>
Cherry-picked to the |
What?
Resolves #45254.
PR tries to fix failing PHPUnit tests.
How?
I've added a check to avoid calling the
gutenberg_resolve_assets
for WP 6.0 and above. The__unstableResolvedAssets
will be generated using_wp_get_iframed_editor_assets
for those versions.Testing Instructions
CI should be green.
Locally:
npm run test:unit:php -- --filter WP_Navigation_Page_Test