Over at #2642122: Overriding already overridden libraries-override requires knowledge of previous libraries-overrides a BC-layer is added to maintain pre-existing behavior of libraries-override for sub themes of base themes that also have libraries-override on the same library assets.
The pre-existing behavior as summarized by @jacine #2642122-18: Overriding already overridden libraries-override requires knowledge of previous libraries-overrides is a bug:

And this is the logic:

Use the original module (or core) namespace for library name.
Use the path of the most recent override (in my case Stable) as the key
Use the full path to the file

The correct behavior should be:

Use the original module (or core) namespace for library name.
Use the originally defined library path as the key
Use the relative path to the file in the current theme as the value

This issue is created to remove the BC-layer

CommentFileSizeAuthor
#3 2852314-3.patch5.39 KBalmaudoh
#2 2852314-2.patch4.32 KBalmaudoh
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

almaudoh created an issue. See original summary.

almaudoh’s picture

almaudoh CreditAttribution: almaudoh commented
Status: Active » Postponed
FileSize
2852314-2.patch4.32 KB

Attached the patch for future BC-removal and postponed.

almaudoh’s picture

almaudoh CreditAttribution: almaudoh commented
FileSize
2852314-3.patch5.39 KB

Updated patch to remove legacy deprecated code.

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.

xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Status: Postponed » Closed (duplicate)

Looks like this was already addressed in a different issue.

acbramley’s picture

acbramley CreditAttribution: acbramley at PreviousNext commented
Version: 9.0.x-dev » 10.0.x-dev
Status: Closed (duplicate) » Postponed

The original fix hasn't been committed yet and therefore the BC layer can't have been removed yet. I think the confusion is from the version this issue was against?

Version: 10.0.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.