-
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
Block Editor: Remove 'React.Children' legacy API in 'Warning' component #67675
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. |
@@ -18,7 +18,9 @@ describe( 'Warning', () => { | |||
|
|||
it( 'should show primary actions', () => { | |||
render( | |||
<Warning actions={ <button>Click me</button> }>Message</Warning> |
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.
I'm not sure why we allowed this behavior. The prop is used and documented as an array.
@@ -18,7 +18,9 @@ describe( 'Warning', () => { | |||
|
|||
it( 'should show primary actions', () => { | |||
render( | |||
<Warning actions={ <button>Click me</button> }>Message</Warning> | |||
<Warning actions={ [ <button key="test">Click me</button> ] }> |
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.
This is an interesting case. Maybe we should account for the case where it's not an array.
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.
I checked, and consumers have always treated actions
as array props since the introduction - #5483.
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.
I don't feel strongly :)
Size Change: -11 B (0%) Total Size: 1.83 MB
ℹ️ View Unchanged
|
I'll merge this and follow up if any bugs are reported. |
What?
PR removes
React.Children
usage from theWarning
component and replaces it with normal array operations.Why?
actions
prop is just an array of action components. It doesn't need a special handling.React.Children
is now a legacy API, and official documentation discourages its use.Testing Instructions
Testing Instructions for Keyboard
Same.
Screenshots or screencast