-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Experiment with contentOnly templateLock on all patterns #64628
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
Conversation
|
Size Change: -144 B (-0.01%) Total Size: 1.77 MB
ℹ️ View Unchanged
|
|
|
||
| const onInsertPattern = useCallback( | ||
| ( blocks, patternName ) => { | ||
| if ( blocks.length === 1 && blocks[ 0 ]?.name === 'core/group' ) { |
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.
@MaggieCabrera @ndiego I wonder if this is a technique we could use as a proxy for "section pattern"?
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.
Yeah perhaps. You might want to include Cover and maybe Media & Text and Columns.
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 have a core pattern that is just a cover block, and I think TT4 has one of those too
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.
Worth noting that not all blocks support templateLock.
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.
If that's the case then we'd need to iterate through the blocks applying the correct blockEditingMode. Template Lock works well for a prototype but possible not for production ready code.
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 realised that we're actually looking to find the block that is acting as the root of all the blocks we conceptually consider to be "sections" on a template/post.
As a result I think it's important that we review #64544 which might give us a standardised way to compute this.
Quick experiment to see how it feels if we add
templateLock: 'contentOnly'to all patterns.