-
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
Remove some low impact APIs that were deprecated on WP 5.3 #34537
Conversation
Size Change: -435 B (0%) Total Size: 1.06 MB
ℹ️ View Unchanged
|
Should we move it to the post editor so it isn't included on other screens? One thing I'm not sure about is how all those screen-specific blocks would work when saved inside the Reusable block. I guess it's something that should be discussed separately anyway.
Should we take one more step and remove all the logic but keep those functions defined with deprecations for one more major release? In general, it sounds like a good plan. |
I guess you're talking about the core/editor to core/block-editor here, right? I'm not sure yet, there's a lot, so I felt it's a bit too soon for these to break. |
I think I misguided you, I was referring to |
Oh for these, I was pretty confident because I checked wpdirectory and also because they really seem like "core" things and things plugin authors would very rarely use. |
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 for the cleanup, Riad! I mostly had a look at the changes in @wordpress/components
.
onClickOutside
forPopover
component: the component still works without it, it might not close when you click outside it.
From a quick look at the code, I don't think that before this PR, clicking outside the popover would close the popover itself — maybe I'm missing something? (Or did you mean that the modal could have been with some 3rd party code in the onClickOutside
callback?)
Also, I can still see traces of the menuLabel
and position
deprecated props in the React Native version of DropdownMenu
👍 from me. These have been properly marked as deprecated for a while. |
43b4c30
to
4bebc09
Compare
I finally got back to this PR and remove the removed props from the native code. I think it's ready. |
Co-authored-by: Marco Ciampini <marco.ciampo@gmail.com>
4bebc09
to
140b1f4
Compare
This PR removes some old APIs that have a low impact and that were deprecated in 5.3.
I also removed some selectors and actions from the 'core/editor' store after checking that it has no impact based on a wpdirectory.net
There are still other APIs that were deprecated on 5.3 that I decided against removing for now because of their potential impact (we could consider removal in future WP major versions):
wp.editor
towp.blockEditor
for some components, selectors and actionswp.components.ServerSideRender
component.What do you think of my arbitrations here?