-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Automatically set reusable to false when a block has a parent defined #35223
Copy link
Copy link
Closed
Labels
Needs DevReady for, and needs developer effortsReady for, and needs developer efforts[Feature] Block APIAPI that allows to express the block paradigm.API that allows to express the block paradigm.[Feature] Synced PatternsRelated to synced patterns (formerly reusable blocks)Related to synced patterns (formerly reusable blocks)[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] EnhancementA suggestion for improvement.A suggestion for improvement.
Metadata
Metadata
Assignees
Labels
Needs DevReady for, and needs developer effortsReady for, and needs developer efforts[Feature] Block APIAPI that allows to express the block paradigm.API that allows to express the block paradigm.[Feature] Synced PatternsRelated to synced patterns (formerly reusable blocks)Related to synced patterns (formerly reusable blocks)[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] EnhancementA suggestion for improvement.A suggestion for improvement.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What problem does this address?
When a block defines a
parentthat means that it gets hidden from the inserter unless you are trying to insert it into the defined parent. The block also cannot be moved outside of the container. However, it is still possible to select the "child" block and make it reusable. You can circumvent this by settingreusabletofalsebut I think that should be the default behavior when a block has aparentdefined.What is your proposed solution?
The possible solution for this would be to automatically set the
reusableflag tofalseby default for when a block has aparentdefined.