CustomSelectControl: Fix menuProps mutation#62149
Conversation
|
I don't think this needs a CHANGELOG entry, but I'm happy to add one if convinced otherwise. |
|
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: +12 B (0%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
mirka
left a comment
There was a problem hiding this comment.
I have an urge to rework this a bit more drastically, but given the practical motivation for this PR and the fact that we'll be entirely replacing this with the v2 Legacy implementation soon, I think this is perfectly sufficient 👍
Co-authored-by: tyxla <tyxla@git.wordpress.org> Co-authored-by: mirka <0mirka00@git.wordpress.org>
Co-authored-by: tyxla <tyxla@git.wordpress.org> Co-authored-by: mirka <0mirka00@git.wordpress.org>
What?
This PR fixes a mutation that we're performing in the
CustomSelectControlcomponent and updates to use a new object instead.Why?
In this particular case, I'm fixing it to resolve an ESLint error that was raised by the React Compiler ESLint plugin in #61788
How?
Using a new object instead of mutating the existing one.
Testing Instructions
Verify the v1
CustomSelectControlcomponent still works.Testing Instructions for Keyboard
None
Screenshots or screencast
None