Skip to content

Pattern Overrides: No opt-out mechanism exists for named overrides #59812

@talldan

Description

@talldan

Problem

Since the PR 'Use block naming for marking blocks as overridable in patterns' was merged, all a user has to do to mark a block within a pattern as overridable is to provide a block name—either using List View, or the input in the 'Advanced' inspector controls.

Currently there's no way to name a block for organizational purposes, and not have it be overridable, which is a problem.

Let's discuss potential solutions to this problem in the comments.

Metadata

Metadata

Assignees

Labels

Needs DesignNeeds design efforts.[Feature] PatternsA collection of blocks that can be synced (previously reusable blocks) or unsynced[Status] In ProgressTracking issues with work in progress[Type] EnhancementA suggestion for improvement.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions