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
defect
Given the following query:
all(`tl.legacy.tabletypes:TLModuleTable`) .filter(module -> $module.get(`tl.legacy.tabletypes:TLModuleTable#name`) == 'DemoTypes') .referers(`tl.legacy.tabletypes:MetaElementTable#module`) .flatten() .filter(type->$type.get(`tl.legacy.tabletypes:MetaElementTable#name`) == 'DemoTypes.A')
The query searches for the type named 'DemoTypes.A' in the TLModule 'DemoTypes'.
If the query is executed without the optimizer, the type is found; if it is executed with the optimizer, the result is empty.
Test
- test.com.top_logic.model.search.expr.TestSearchExpression.testModelNavigation()
- Entering the above query in the model-based search
- Expected: The result contains one row: the type DemoTypes:DemoTypes.A
Additional test:
Returns no results:
{
attr = all(`tl.legacy.tabletypes:MetaAttributeTable`)
.filter(a -> $a.get(`tl.legacy.tabletypes:MetaAttributeTable#name`) == "containment")
.filter(a -> $a.get(`tl.legacy.tabletypes:MetaAttributeTable#name`) == `DemoTypes:DemoTypes.A`);
$attr;
}
In contrast, this returns the following result:
all(`tl.legacy.tabletypes:MetaAttributeTable`)
.filter(a -> $a.get(`tl.legacy.tabletypes:MetaAttributeTable#name`) == "containment")
.filter(a -> $a.get(`tl.legacy.tabletypes:MetaAttributeTable#owner`) == `DemoTypes:DemoTypes.A`)