Details
-
Task
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Description
Lately, the Dom around qualified names changed and all features that existed before it might not have been adapted to the new qualified names.
One should test if various qmlls features still work correctly by adding more testcases to:
- find definition,
- find type definition,
- find Base object,
- find definition from location and
- resolve expression type
- (that is almost everything except findUsages more or less)
tests.
The idea here is to go through the various Dom structures that changed to be able to support qualified names and see if the various qmlls features (still) work correctly on them.
List of Dom structures to go through:
- The left hand side of Bindings, e.g. someItem.property: 42
- Property and signal definitions, e.g. signal mySignal() or property int myProperty
- type annotations, e.g. function f(x: QQ.Item) {} or function f(): QQ.Item {}
- Qml Component name in instantiations, e.g. QQ.Item {} in default and normal bindings
- Qml Component name in definitions, e.g. component MyIC: QQ.Item {}
- Qml Component type in definitions, e.g. component MyIC: QQ.Item {}
- Qualified names in JS snippets, like return someItem.property
Attachments
Issue Links
- is required for
-
QTBUG-119964 New QML LSP features (6.8)
- In Progress
- resulted from
-
QTBUG-114990 qmlls: find usages of Qml Types
- Closed