-
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
Relocate 'ErrorBoundary' component unit test folders #59031
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. |
Size Change: 0 B Total Size: 1.71 MB ℹ️ View Unchanged
|
Flaky tests detected in d81969e. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7905941293
|
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.
🆗
Thanks for the review, @draganescu! |
Note that as part of curating the Gutenberg 17.8 changelog, I added the label [Type] Code Quality to this PR to better categorize it. Please let me know if there is a different label that would be a better fit. |
What?
This is a follow-up to #42024.
PR moves the
ErrorBoundary
unit tests into the component folders + minor coding standard updates.Why?
Matches to the guidelines the project uses for other component unit tests.
Testing Instructions
CI cheks are green.