Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.15.0 Beta3
-
e52e7ad76edc6012285db6c83eb12e8724a234ac 6d3aae3cf47fbf21bd27eda7a249c2a23308156e
Description
The qmltypes format has a field "dependencies". This field can contain a list of URIs of other modules. qmlplugindump and qmltyperegistrar generate these by copying the dependencies.json file given as argument into it.
No tool, as far as I can see evaluates the dependencies. Furthermore, it is currently unclear how to handle types from other modules we depend on in qmltypes. For example, the type "QtQuick/Application" belongs to QtQuick and its C++ type QQuickApplication derives from QQmlApplication. That type is defined in QtQml, but not exported to QML. Therefore, it appears as anonymous dependent type in QtQuick's plugins.qmltypes. What should happen if QQmlApplication was exported to QML in QtQml?
As additional food for though, we do have "import" as well as "depends" fields in qmldir. "import" imports the given, not necessarily related module into the same namespace. "depends" in qmldir is also unclear to me.
We need to clarify what these fields should mean and use them correctly.