#27264 Selection components should not unpack one-element sets

enhancement

major

#26283

In-app configured global dialogs

#27411

Smart Startup/Shutdown

#27431

Deploy App Archetype to MavenCentral

minor

#27248

Predefine icons/cliques for buttons/dialogs with theme variables if possible

#27264

Selection components should not unpack one-element sets

#27267

ListModelBuilder shall return a collection in getModel(...).

#27365

Select default selection based on the last (current) selection

#27412

Bulk Dependency Update 2023/06

defect

major

#27388

No display of error text in composition tables

#27407

Selection of the grid disappears with F5

#27408

AbstractFlexDataManager logs warning when loading the same object multiple times

#27446

Incorrect license display for TopLogic modules in the license overview

minor

#27230

Command release service: exception rule does not work

#27275

I18N string as name attribute returns error

#27306

Option providers still do not update calculated suggested values

#27312

Application tests: No recording of inputs in I18N string attributes in grid possible

#27326

Memory hole: Personal configuration is not cleared properly

#27340

Administration: Maintenance mode does not work properly

#27341

TL script: NPE when regular expressions evaluate to "null".

#27343

LayoutEditor: Component channel selection for dialog open buttons wrong

#27344

Unwanted inlining of properties when creating a new app

#27349

Disappearing design buttons in tiles

#27364

Scheduler: Task execution fails with longer results

#27381

Incorrect preassignment in the chart JS template

#27385

Incorrect calculation of the sort order in references

#27400

ResKey: Missing quoting of non-primitive arguments

#27403

Synthetic `UpdateChainLink` chain of `KBDataProducerTask` leads nowhere

#27427

Potential NullPointerException when sorting the results of a quick search

#27429

Assertion error when setting incompatible value in ComplexField

enhancement

minor

#27264

Selection components should not unpack one-element sets

LayoutFramework RequiresMigration

Currently, Top-Logic’s approach is that in selection components (tl:TableComponent, tl:TreeComponent, tl:TreeTableComponent, and tl:GridComponent) that support multiple selections, single-element and empty selections are handled in a special way: Instead of a single-element set, the “one” element is written to the selection channel, and in the case of an empty selection, “null” is written.

Improvement

If the component supports single selection, getSelected() returns either the selected object or null if nothing is selected.

If the component supports multiple selection, getSelected() is always a collection, which may be empty if nothing is selected.

Code Migration

Components that use the selection of a tl:TableComponent, tl:TreeComponent, tl:TreeTableComponent, or tl:GridComponent with multiple selection as a model must be adapted, since the selection is now always a collection.

For example, a `tl:TransformLinkingByExpression` can be used here. From a `tl:CommandHandler` configuration

target="selection(<component>)"

becomes

<target class="com.top_logic.model.search.providers.TransformLinkingByExpression"
 input="selection(<component>)"
>
 <function><![CDATA[selection -> if ($selection.size() <= 1,  $selection.singleElement(), null)]]></function>
</target>

Example

In the demo, under Technical Demo > Components > Tables and Trees, there are examples of selection components with multiple selection and single selection.

Test

TestTreeTableMultiSelection.script.xml, TestTreeMultiSelection.script.xml, TestTableMultiSelection.script.xml, TestGridMultiSelection.script.xml.