Problem
The tests at QTBUG-137199 show that qmllint and qmlls can receive different import paths and produce different warnings from each other.

This is confusing: Developers rely on qmllint and qmlls to assess the correctness of their QML project. Having discrepancies between the code editor window and the compilation output does not inspire confidence.

Suggestions

We could simply try to ensure that the build system passes the same list of import paths to both qmllint and qmlls. However, there is still a risk that a future change causes divergence again.

Is there a way to pass import paths to both tools via a shared mechanism? (Currently, qmllint reads *.rsp files while qmlls reads .qmlls.build.ini files - Could they read from a common file instead?)