major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
enhancement
In the "defaultFor " layout configuration, you can define a component as the default for a `tl:TLClass`. This is done by configuring the module-local name, which is not unique.
Instead, the fully qualified name should be used.
Furthermore, the name of a `tl:MetaObject` can be configured. Here, too, the qualified name of the associated `tl:TLClass` should be used instead.
Code Migration
- In layout XML files, search for assignments to the `handles` property in `tl:BoundComponent` and assign these values to the ` defaultFor ` property instead.
- In layout XML files, search for ` defaultFor ` assignments in component configurations:
- Replace the names of tl:TLClass with the qualified name, i.e., prefix the local name with the module name followed by a colon (:).
- Replace the names of tl:MetaObjects (i.e., types for which there is no model definition, such as Person or Group) with the name of the synthetic tl:TLClass: If the MetaObject is named XXX, it must be replaced with `tl.legacy.tabletypes:XXXTable`.
Test
No test, refactoring.