Problem/Motivation

In the components library, the "other" group is displayed in first position, while in UIP1 it was sorted alphabetically by group name.

Steps to reproduce

Try with UI Suite Bootstrap.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

grimreaper created an issue. See original summary.

pdureau’s picture

Title: Library: other group placed first » [2.0.0beta5] Library: other group placed first
Assigned: Unassigned » grimreaper
Status: Active » Postponed

If the expected change is in ComponentPluginManager::getSortedDefinitions() , the CategorizingPluginManagerInterface logic will move to Core: #3474533: ComponentPluginManager must implement CategorizingPluginManagerInterface https://git.drupalcode.org/project/drupal/-/merge_requests/10245/diffs Is it going the way you expect?

If the expected change is elsewhere, do you want to propose a change?

grimreaper’s picture

Status: Postponed » Active
pdureau’s picture

Title: [2.0.0beta5] Library: other group placed first » [2.0.0-beta5] Library: other group placed first
pdureau’s picture

Title: [2.0.0-beta5] Library: other group placed first » [2.0.0-rc1] Library: other group placed first
grimreaper’s picture

grimreaper’s picture

Assigned: grimreaper » Unassigned
Status: Active » Postponed

This requires the change from the parent core issue.

Also wondering if possible to only override the methods signature to have by default label key as name.

grimreaper’s picture

Assigned: Unassigned » grimreaper
Status: Postponed » Needs work

grimreaper’s picture

Assigned: grimreaper » pdureau
Status: Needs work » Needs review

New MR created and this one can wait for the core issue.

Also will comment in code review on the core issue. because component key is name and not label.

pdureau’s picture

Assigned: pdureau » Unassigned
Status: Needs review » Reviewed & tested by the community

Expects auto merged

pdureau’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.