-
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
Navigation: Remove the Gutenberg plugin check #47579
Conversation
Size Change: -236 B (0%) Total Size: 1.31 MB
ℹ️ View Unchanged
|
Flaky tests detected in 8626cfe. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4046663435
|
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.
Excellent cleanup with this. This PR removes all the conditions that kept the pre experiment behavior around, making sure this UX for the navigation block lands in core in the next release.
Given the component that enables it is now exported as an experiment and in my testing this PR does not break anything, lets 🚢 it!
What?
Now that this component is marked as an experiment (#47465), we can remove the IS_GUTENBERG_PLUGIN check from this code.
Why?
This will allow the experimental component to be part of the 6.2 release without risking other developers using it.
How?
Just removes the IS_GUTENBERG_PLUGIN conditionals.
Testing Instructions
Testing Instructions for Keyboard
As above