Details
-
Suggestion
-
Resolution: Fixed
-
P3: Somewhat important
-
6.2, 6.3, 6.4
-
a9038a6cc6ba79feefa38213b89d9b5ce73cb12d
Description
Currently our warnings are rather free-form. We should consider giving them ids (either numbers or names):
The advantage would be that they
- allow you to
have a table with more details like https://doc.qt.io/qtcreator/creator-checking-code-syntax.html#javascript-and-qml-error-codes, - can be parsed in an IDE if you add them as a special JSON field
and lastly, - would even allow some dedicated pages like doc.qt.io/qmllint/issues/<ID> with a description of the issue and a recommended way how to fix them (basically, a better version of 1)
For prior art, see https://doc.rust-lang.org/error-index.html for how Rust does it
Attachments
Issue Links
- resulted in
-
QTBUG-111137 Create doc pages that explain how to fix qmllint/qmlsc warnings
- Closed
- split to
-
QTBUG-111137 Create doc pages that explain how to fix qmllint/qmlsc warnings
- Closed
For Gerrit Dashboard: QTBUG-103453 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
415179,11 | QQmlJSLogger: Switch to an ID based system | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
420113,2 | Adapt to new logging system | dev | qt/tqtc-qmlcompilerplus | Status: MERGED | +2 | 0 |