-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Block JSON schema: add visibility key to supports definition #73612
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. |
t-hamano
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.
Nice catch!
Can you add the visibility section to the end of this file following the format of the other sections?
Co-authored-by: Aki Hamano <[email protected]>
|
@t-hamano |
t-hamano
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.
LGTM!
|
Flaky tests detected in d8e276f. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19734122611
|
What?
Related #57373
This PR adds
visibilitykey to supports definition in block.json schema.Why?
How?
Testing Instructions
You should see the
visibilitykey listed in the supports property.