Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.8
-
None
-
96b29e720 (dev), e3ed72d7e (dev), 35f9ff8c1 (6.8), 290336814 (6.8), 4278f0246 (6.7), 54a352b43 (tqtc/lts-6.5), 6d3777b6e (tqtc/lts-6.2)
Description
https://codereview.qt-project.org/c/qt/qtdeclarative/+/541680 changed the code we generate for enums to only apply the scoped marker if enums are registered with
"RegisterEnumClassesUnscoped" being set to false
(compare https://codereview.qt-project.org/c/qt/qtdeclarative/+/541680/6/src/qmltyperegistrar/qqmltypescreator.cpp#363)
This confuses the qmllint logic, which intends to warn about usages like
`Type.EnumName.EnumEntry`. However, while this is not mandatory with enum classes (unless said "RegisterEnumClassesUnscoped" is added), it' still possible.
We need to have a way to distinguish "scoped enums" from "only scoped enums".
Attachments
Issue Links
- resulted from
-
QTBUG-107143 qmllint ignore RegisterEnumClassesUnscoped
- Closed
For Gerrit Dashboard: QTBUG-127308 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
594233,2 | Fix enum scoping rules | tqtc/lts-6.2 | qt/tqtc-qmlcompilerplus | Status: NEW | +2 | 0 |
590070,5 | QmlCompiler: Fix enum scoping rules | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
590136,3 | QmlCompiler: Fix logic for suggesting enum values as "didYouMean" | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
592320,3 | QmlCompiler: Fix enum scoping rules | 6.8 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
592325,3 | QmlCompiler: Fix logic for suggesting enum values as "didYouMean" | 6.8 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
592530,3 | QmlCompiler: Fix enum scoping rules | 6.7 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
593215,3 | QmlCompiler: Fix enum scoping rules | tqtc/lts-6.5 | qt/tqtc-qtdeclarative | Status: MERGED | +2 | 0 |
593971,3 | QmlCompiler: Fix enum scoping rules | tqtc/lts-6.2 | qt/tqtc-qtdeclarative | Status: MERGED | +2 | 0 |