What is the bug or the crash?
Having the enum QgsProcessing.TypeVectorLine leads to the suggestion Enum error, add 'ProcessingSourceType' before 'TypeVectorLine' which would lead to QgsProcessing.ProcessingSourceType.TypeVectorLine which is wrong.
The correct enum would be QgsProcessing.SourceType.TypeVectorLine if compatibility with QGIS <3.36 is wanted or Qgis.ProcessingSourceType.VectorLine if QGIS >=3.36 is ok.
Same for e.g. QgsProcessingParameterNumber.Double where the script suggests the wrong QgsProcessingParameterNumber.ProcessingNumberParameterType.Double.
Correct would be either QgsProcessingParameterNumber.Type.Double (QGIS <3.36) or Qgis.ProcessingNumberParameterType.Double (QGIS >=3.36).
I assume the same happens for other Processing related enums.
References:
Steps to reproduce the issue
See above
Versions
Latest qt5_to_qt6.py (I presume) via registry.gitlab.com/oslandia/qgis/pyqgis-4-checker/pyqgis-qt-checker:latest
Supported QGIS version
New profile
Additional context
No response
What is the bug or the crash?
Having the enum
QgsProcessing.TypeVectorLineleads to the suggestionEnum error, add 'ProcessingSourceType' before 'TypeVectorLine'which would lead toQgsProcessing.ProcessingSourceType.TypeVectorLinewhich is wrong.The correct enum would be
QgsProcessing.SourceType.TypeVectorLineif compatibility with QGIS <3.36 is wanted orQgis.ProcessingSourceType.VectorLineif QGIS >=3.36 is ok.Same for e.g.
QgsProcessingParameterNumber.Doublewhere the script suggests the wrongQgsProcessingParameterNumber.ProcessingNumberParameterType.Double.Correct would be either
QgsProcessingParameterNumber.Type.Double(QGIS <3.36) orQgis.ProcessingNumberParameterType.Double(QGIS >=3.36).I assume the same happens for other Processing related enums.
References:
Steps to reproduce the issue
See above
Versions
Latest
qt5_to_qt6.py(I presume) viaregistry.gitlab.com/oslandia/qgis/pyqgis-4-checker/pyqgis-qt-checker:latestSupported QGIS version
New profile
Additional context
No response