https://codereview.qt-project.org/c/qt/qtpositioning/+/435520 brought some improvements to the QML value types of this module. The documentation should be updated to reflect this.

• We should document the formal QML names (tracked at QTBUG-139780)
• https://doc.qt.io/qt-6/qml-qtpositioning-location.html says that, for the "coordinate" and "boundingShape" properties, "This property's changed() signal is currently emitted only if the whole object changes, not if only the contents of the object change." This is, thankfully, no longer true.
• Numerous places in the documentation say, "Use properties of type \l var to store a <VALUE_TYPE>" (Example: https://doc.qt.io/qt-6/qml-coordinate.html#example-usage ). The patch has made it unnecessary to use var, so it should now be discouraged (see QTBUG-138665).
• https://doc.qt.io/qt-6/positioning-cpp-qml.html#direct-c-value-integration-in-qtpositioning still shows the old QML_ANONYMOUS implementation of the value types, which no longer reflects the current implementation.
  • IMHO, we don't actually need to document the internal implementation details to that extent. The important thing is to show how to use the API.