Details
-
Suggestion
-
Resolution: Unresolved
-
P2: Important
-
None
-
None
Description
In our old and huge QML code base we have JavaScript functions in the QML root object that provide frequently used L10N and layouting features. They are used via unqualified access and this won't change unless we decide to throw away the entire code base.
Sadly this set design choise collides massively with qmllint's continiously improving ability to discover unqualified access. For many of your QML modules Qt Creator is nothing but a huge, yellow qmllint warning mess because of this unqualified access, rendering both Qt Creator and qmllint entirely useless for our project.
Please add a method to instruct qmllint about intentional unqualified access. Be it an external configuration file. Be it annotations to the functions which are used by intentional unqualified access. Be it via some C++ API to register globally accessible JavaScript functions.
Please help!
Attachments
Issue Links
- relates to
-
QTBUG-128232 qmlls: add crude support for context properties
-
- In Progress
-