-
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
Handle block metadata attribute and related experimental APIs #47791
Conversation
Size Change: +14 B (0%) Total Size: 1.33 MB
ℹ️ View Unchanged
|
@ntsekouras Sorry if it seems obvious but what do you see as the next steps here? |
3f9e6cc
to
db02a6a
Compare
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 Dave!
This PR's |
3435c8f
to
774d503
Compare
Flaky tests detected in 774d503. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4144068864
|
I just cherry-picked this PR to the wp/6.2 branch to get it included in the next release: a6bc65a |
* Move PHP attribute registration to experiments dir * Limit __experimentalMetadata to Core blocks * fix check --------- Co-authored-by: ntsekouras <[email protected]>
What?
Attempts to avoid releasing
__experimentalMetadata
and associated blockmetadata
attribute in WP 6.2.Why?
Audit of experimental APIs for 6.2 flagged it.
After discussing with @ntsekouras (away from Github) we settled on avoiding the APIs being released at all outside of the Plugin.
How?
compat/6.1
and into thelib/experiments/
dir.Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast