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

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

    XMLWordPrintable

Details

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

    Description

      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)

      Attachments

        Issue Links

          covers

          Bug - A problem which impairs or prevents the functions of the product. QDS-10695 Qt Design Studio tutorials are broken

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-110827 Qt's Gallery example producing tons of warning/errors

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Task - A task that needs to be done. QDS-9809 Qt Quick Studio Components/Effects: Fix compilation warnings

          • Not Evaluated - Not yet evaluated/prioritized
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-111176 Views pass either "model" or "modelData" to delegates, depending on type of model

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          split to

          Task - A task that needs to be done. QTBUG-131978 Update our published QML code to reflect current best practices

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • In Progress
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

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

              Dates

                Created:
                Updated: