Add a ThemeRegistryAlter attribute

Created on 4 August 2024, 8 months ago

Problem/Motivation

Sometimes there are theme hooks/templates provided by core/other modules where we might want to sub in a design-system template instead of writing a thin wrapper template.
In such cases it would be neat if we could add a #[ThemeRegistryAlter('{theme hook}')] to enums to have their path/libraries registered as the path for a template/hook provided by another module.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @larowlan
  • Status changed to Closed: won't fix 2 days ago
  • πŸ‡¦πŸ‡ΊAustralia dpi Perth, Australia

    The new CanonicalProduct and Slots attr via php extends inheritance should fulfill the requirements here.

    With these systems, you can sub in your own twig/js/css, but inherit from slots and a parent object.

    Futher, Slots are the recommended way of working, and they dont have a much surface thats hookable.

    If these are not a good solution, let me know!

Production build 0.71.5 2024