Experiment with contentOnly templateLock on all patterns#64628
Experiment with contentOnly templateLock on all patterns#64628noisysocks wants to merge 1 commit intotrunkfrom
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.
@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.
Yeah perhaps. You might want to include Cover and maybe Media & Text and Columns.
There was a problem hiding this comment.
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.
Worth noting that not all blocks support templateLock.
There was a problem hiding this comment.
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.
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.