-
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
Plugin: Bump minimum WordPress version to 5.3 #20628
Conversation
Size Change: -2.26 kB (0%) Total Size: 863 kB
ℹ️ View Unchanged
|
We also can remove |
@mcsf That looks good to me, thanks for handling that! |
I would keep |
@gziolo Ok, then we should adjust the the TODO inside the function: gutenberg/lib/client-assets.php Lines 214 to 215 in 287498f
|
8bdd5ee
to
9ac1e2a
Compare
Confirmed via: https://github.com/WordPress/WordPress/blob/5.3/wp-admin/edit-form-blocks.php#L51 |
I don't think we need the React or Lodash registrations? As of WordPress 5.3, the versions are the same as what we're overriding: https://github.com/WordPress/WordPress/blob/5.3/wp-includes/script-loader.php#L94-L97 To @gziolo's point in #20628 (comment), it might be something where we want to keep the function for the sake of anticipating some future use. I don't feel strongly one way or the other, but it would be easy enough to refer back to the history of the file to restore the function if and when it's needed once more. |
I really don't feel strongly about this; I can either remove |
I'd suggest to just remove it altogether. |
I starting doing this, then realised that I've tentatively pushed 1be218b. Thoughts? |
Fair enough. I don't feel too strongly about it, and agree that it would be a pain to bring everything back in place at a later point. One suggestion I might make is to include an inline code comment explaining why we have an empty function there. |
Agreed, a code comment with a link to this PR should make it easier to restore code when we need another override in the future. |
Done. |
I'm glad you raised the point about the plugin build script and its implementation for downloading vendor dependencies. In revisiting my own #20225, I sense that the use of https://plugins.trac.wordpress.org/browser/gutenberg/tags/7.6.0/vendor Trying to think how best to address this (without also needlessly blocking this pull request or #20225). I imagine the solution would be one of either (a) move these |
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.
Per my previous comment, I think it will be easiest to merge this, then I can rebase my other pull request with the necessary changes to account for the polyfill vendor scripts.
The changes here look sensible to me 👍
Thanks, I appreciate the deep dive and unblocking. |
Description
Fixes #20484
With the release of RC1 for WordPress 5.4, and given the constraints raised in #20484, this PR bumps the required WordPress version for running the Gutenberg plugin from 5.2 to 5.3.
In the process, this PR eliminates the interception of core's
block_editor_preload_paths
filter, which was in place to provide compatibility for the following features:@talldan, @aduth: As authors of the aforementioned PRs, could you confirm these removals for me?
How has this been tested?
Screenshots
Types of changes
Checklist: