• Icon: Technical task Technical task
    • Resolution: Fixed
    • Icon: P2: Important P2: Important
    • 6.9
    • QML: Tooling
    • None
    • df2e55d92 (14.0), c2b5be2e2 (dev), 09c2bb98c (dev), f4e02ece6 (dev), 538dd8b26 (6.8), cc683ae53 (6.8), dc569efd7 (6.8), fc26ad58e (dev), c70bba6d8 (6.8), b3b359548 (master), 52abfab8a (master), 6cb958de9 (master), 180f57e66 (master)

      Currently, semantic highlighting provides token information coarsely than the embedded code model highligher in Qt Creator. We need more fine grained token information to reach feature parity with Qt Creator.

      Make sure that introducing new token types shouldn't break the other text editor's interpretation of the token data. You should get this from the client capability.

      Consider the following labels in QtCreator:

      QML Binding

      Qml Local Id

      Qml Root Object Property ?? What is this?

      Qml Scope Object Property ?? What is this?

      Qml State name

      Qml Type name

      Qml External Id

      Qml External Object Property

      JavaScript Scope Var

      JavaScript Import

      JavaScript Global Variable

      Punctuation

        For Gerrit Dashboard: QTBUG-126550
        # Subject Branch Project Status CR V

            semih.yavuz Semih Yavuz
            semih.yavuz Semih Yavuz
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: