-
Notifications
You must be signed in to change notification settings - Fork 798
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
Blocks: move from editor to block-editor #14047
Conversation
Now that Jetpack will require WordPress 5.2, we can update our blocks to use the @wordpress/block-editor package that was added in WP 5.2. This will get rid of a few deprecated messages that were present when using the block editor.
Caution: This PR has changes that must be merged to WordPress.com |
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: November 18, 2019. |
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've run through these blocks, they all appear to be functioning correctly (except for some unrelated issues I ran into with the Map block: #14057, #14058).
I've also confirmed that remaining uses of @wordpress/editor
are correct.
@wordpress/block-editor
should probably be added to package.json
.
Otherwise, looks good to me!
Since They need to be added in some special cases though, I think if we depend on them in unit tests for example. |
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 haven't tested but overall looks good. 👍
Thanks for taking on it!
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.
Ran through all the blocks quickly, including paid ones. Adding them at the basic level and viewing on front-end. All seemed to work well with no console errors.
jeherve, Your synced wpcom patch D35538-code has been updated. |
* 8.0 Release: running changelog * Changelog: add #13921 * Changelog: add #13980 * Changelog: add #13905 * Changelog: add #13971 * Changelog: add #13984 * Changelog: add #14009 * Changelog: add #13620 * Remove things that will ship in 7.9.1 * Changelog: add 7.9.1 release (#14044) * Changelog: add base for 7.9.1 release * Update release date and post link * Changelog: add #14066 * Update changelog for 7.9.1 * Changelog: add #13405 * Changelog: add #13841 * Changelog: add #13924 * Changelog: add #13986 * Changelog: add #14010, #14028, #14053, #14055. * Changelog: add #14054 * Changelog: add #14031 * Changelog: add #14039 * Changelog: add #14050 * Changelog: add #14070 * Changelog: add #14082 * Changelog: add #14084 * Changelog: add #14111 * Changelog: add #13961 * Changelog: add #14047 * Changelog: add #14091 * Changelog: add #14108 * Changelog: add #14121
Changes proposed in this Pull Request:
Now that Jetpack will require WordPress 5.2 (see #13620), we can update our blocks to use the
@wordpress/block-editor
package that was added in WP 5.2.This will get rid of a few deprecated messages that were present when using the block editor.
Testing instructions:
Proposed changelog entry for your changes: