Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-110934

Make our published QML code as free of qmllint errors/warnings as possible

XMLWordPrintable

    • 6dcaaca3a (dev), 6b2e05d9c (6.5), b9db5246b (6.4), 05c16d8e1 (dev), 5ee0ed790 (6.5)

      Suggestion

      For both our source code and our published examples, establish tools and processes (manual or automatic) to achieve the following:

      1. Identify all the warnings that are now fixable
      2. Avoid introducing new fixable warnings

       

      Why?

      Because our published examples are meant to be used as references, and because https://doc.qt.io/qt-6/qtquickcontrols2-customize.html instructs users to copy our code from $QTDIR/qml/QtQuick/Controls/Basic/

      Some possible outcomes of such processes are:

      • When a new example is added, its warnings are reviewed and the fixable ones are fixed earlier (so QTBUG-110831 would've been prevented or addressed earlier)
      • When a new pragma is introduced, we would have be alerted to the places in our existing code that needs this pragma (so https://codereview.qt-project.org/c/qt/qtdeclarative/+/459949 would've been part of the Qt 6.4.0 release)

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            qtqmlteam Qt Qml Team User
            skoh-qt Sze Howe Koh
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: