Library ordering should follow subtheme hierarchy to match pre-10.4/11.1 logic

Created on 6 March 2025, about 1 month ago

Problem/Motivation

In 11.1/10.4 the asset library loading logic was modified to be more stringent based upon the library's dependencies. This excluded the implicit dependency expectation when using a subtheme.

Steps to reproduce

Create a subtheme of a core theme.
Add a CSS library that is loaded by the subtheme.

Expected behavior:
* The new CSS file is loaded after the parent theme's CSS files.

Actual behavior:
* The new CSS file will not necessarily be loaded after the parent theme's CSS files.

Proposed resolution

The library ordering logic take into consideration subtheme hierarchy to place subtheme's libraries after the parent theme's.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Active

Version

11.0 🔥

Component

asset library system

Created by

🇺🇸United States DamienMcKenna NH, USA

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

Comments & Activities

Production build 0.71.5 2024