-
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
Remove unnecessary/incorrect unlock
call in setEditorMode
action
#64073
Conversation
Size Change: +1 B (0%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
To test this, I ran |
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. |
I haven't debugged why yet, but without the |
OK - looks like block editor settings does have a notion of I'll revert this, as it does seem like the |
What?
Small PR that removes an unnecessary
unlock
call.Why?
First I noticed that the code is doing it wrong (it should unlock the
select
), but then I noticed thatgetSettings
isn't private, so the unlock does nothing (settings is also not locked).How?
Deletes it