Skip to content

Move the Pattern Overrides feature to the block editor package #65486

@talldan

Description

@talldan

Description

The pattern overrides feature currently exists primarily in the @wordpress/editor package as an extension to the default block editor.

This has caused some issues though, most recently documented in #65058. The added complexity isn't ideal, and it also likely causes some performance issues.

In a brief conversation with recently, @youknowriad mentioned an alternative, that pattern overrides could be considered a @wordpress/block-editor package feature.

Doing so would allow for removing the use of filters/slots to extend parts of the editor, and tidy up the code considerably.

The steps would be:

Metadata

Metadata

Assignees

No one assigned

    Labels

    [Feature] Block bindings[Feature] PatternsA collection of blocks that can be synced (previously reusable blocks) or unsynced[Type] Code QualityIssues or PRs that relate to code quality

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions