[PAGES-5] Add comparator class for sorting available components list Created: 04/Feb/15  Updated: 20/Feb/15  Resolved: 12/Feb/15

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLUI-3347 CLONE - Add comparator class for sort... Closed
dependency
depends upon MGNLUI-3215 Page & component chooser field (avail... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Currently, building options for available component templates is hard-coded in CreateComponentAction, while ComponentSelectorDefinition/FieldFactory is unused.

As MGNLUI-3215 brings possibility of specifying comparatorClass on any SelectFieldDefinition, we should make use of this for the newComponent dialog, i.e. move this dialog definition to configuration.

-As we're programmatically creating the select field for the available components we need to add the options to the actin definition itself.-



 Comments   
Comment by Mikaël Geljić [ 11/Feb/15 ]

Reopening/reassigning,

Let's just port what was done in MGNLUI-3347 to pages 5.4 too, i.e. moving newComponent dialog from hard-coded in CreateComponentAction to config. Then setting comparatorClass for component selector is granted, and is done the same way as for sorting page templates.

Generated at Mon Feb 12 06:14:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.