Details
-
Technical task
-
Resolution: Fixed
-
Not Evaluated
-
None
-
None
Description
Before we are able to create a safe QQmlJSScope API replacement we must first narrow down what this API needs to be capable of. For that purpose we should first write a bunch of passes based on existing ideas for qmllint features that were thus far unfeasible because i.e. they were Qt Quick specific.
Then by trying to port these to the new API we will easily be able to find out whether it is capable enough or not.
Attachments
Issue Links
- depends on
-
QTBUG-102859
Reimplement all feasible qmlWarning() warnings in qmllint
-
- Closed
-
- is required for
-
QTBUG-102276
Create abstraction layer for QQmlJSScope
-
- Closed
-
| For Gerrit Dashboard: QTBUG-102277 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 405855,10 | qmllint/Quick: Warn about customizing native QtQuick.Controls styles | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
| 407347,13 | QmlLintQuickPlugin: Warn about disallowed positioning properties | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
| 407605,3 | QmlLintQuickPlugin: Warn about attached types used in wrong elements | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
| 408971,5 | QmlLintQuickPlugin: Warn about various SwipeDelegate issues | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |