-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Editor: Update WordPress packages published for Gutenberg 10.6 #1257
Conversation
@@ -1003,7 +1003,7 @@ module.exports = function(grunt) { | |||
WORKING_DIR + 'wp-{admin,includes}/**/*.js', | |||
WORKING_DIR + 'wp-content/themes/twenty*/**/*.js', | |||
'!' + WORKING_DIR + 'wp-content/themes/twenty*/node_modules/**/*.js', | |||
'!' + WORKING_DIR + 'wp-includes/js/dist/vendor/*.js', | |||
'!' + WORKING_DIR + 'wp-includes/js/dist/**/*.js', |
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.
We no longer publish ES5 code to npm. All WordPress packages work with ES2015+ from now on.
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.
Can you clarify the change a bit more :p
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.
This excludes WP packages from JSHint validation. js/dist
folder contains files built from node_modules
with webpack.
I updated the todo list with a few required items as well. |
Site Logo block registers 3 filters in addition to block registration: Do you think we should apply those changes directly to WP core? Those changes fail 2 unit tests:
I think those filters will get executed twice once we land the block in WP core. |
@@ -0,0 +1,392 @@ | |||
<?php | |||
/** | |||
* Duotone block support flag. |
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.
As discussed in WordPress/gutenberg#26752 (comment) with @ajlende, we need to include the license detailed for the code derived from the TinyColor
library.
I scanned quickly changes applied between 10.5 and 10.6 and I might have covered all of them with the last commit. We need to double-check: WordPress/gutenberg@release/10.5...release/10.6. I backported all changes for block supports in 934ec7a. I left there 2 TODO items where I had to removed logic that depends on Global Styles in the layout support. It's something we need to explicitly list for the next round so it's wired correctly. |
|
||
$used_layout = $block['attrs']['layout']; | ||
if ( isset( $used_layout['inherit'] ) && $used_layout['inherit'] ) { | ||
// TODO: Add theme.json handling for the default layout. |
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.
@youknowriad, it might be that you didn't backport this part earlier because it makes sense only when Global Styles are in place.
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.
Yes, I left the whole "layout" support for later (when theme.json lands) because it should be disabled for themes without that.
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.
Right, so we probably can remove it here as well. It's most likely dead code anyway.
I found the logic that is related to:
It looks like something that could be done separately. |
( true === _wp_array_get( $block_type->supports, array( '__experimentalBorder' ), $default ) ) | ||
) { | ||
return true; | ||
} |
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.
This part can probably use block_has_support
as well without the nested $feature
thing but I guess that comment is better in the Gutenberg repo :)
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.
Yes, let's fix in Gutenberg and backport with 10.7 version.
@gziolo did we include the 10.6.1 package update and php changes here? |
If 10.6.1 was published this week, then the answer is no. |
I noticed that the editor styles are not applied properly (compared to the plugin), not sure why. You can compare with tt1 theme, you'll see that the background is not applied |
Nevermind, I was testing with tt1-blocks and theme.json based styles are not backported yet, so we're all good here. |
Looking at the iframe stuff. Trying to get this branch running first. |
I removed the Site Logo block for now because it creates too much friction, and I couldn't find a simple way to make failing tests pass without changing assertions. It needs to be investigated separately. Technically speaking, this block will be still exposed in the inserter, but it won't work correctly until we include PHP bits. |
Closed with https://core.trac.wordpress.org/changeset/50929. |
Trac ticket: https://core.trac.wordpress.org/ticket/52991
TODO
It needs more work:
Changes to– it looks up to datelib/block-patterns/three-columns-media-text.php
patternSome php changes to support the iframed template editor cc @ellatrix– it's tracked separately and it depends on other changesThis Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.