From df179c52ec02aec91058d6977e08a405932af2bd Mon Sep 17 00:00:00 2001 From: Ulf Hermann Date: Fri, 13 Nov 2020 13:40:56 +0100 Subject: QmlCompiler: Fix resolution of method and property types We need to resolve the types for QML elements in two passes because only after finishing the parsing we have the QML-declared methods and properties available. We already need the base type before, though. Also, there can be multiple methods of the same name. We need API to access them. It also turns out that the internal name of the "var" type has to be QVariant in order to match reality. "var" properties and unnamed arguments to JS functions are implemented as QVariant. Change-Id: I541f11e96db72d832f4e4443d3a5d31079a56575 Reviewed-by: Fabian Kosmale --- src/imports/builtins/builtins.qmltypes | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'src/imports/builtins/builtins.qmltypes') diff --git a/src/imports/builtins/builtins.qmltypes b/src/imports/builtins/builtins.qmltypes index 909dab7707..572673e5c1 100644 --- a/src/imports/builtins/builtins.qmltypes +++ b/src/imports/builtins/builtins.qmltypes @@ -10,12 +10,17 @@ Module { } Component { - name: "QJSValue" + name: "QVariant" accessSemantics: "value" exports: ["QML/var 1.0", "QML/variant 1.0"] exportMetaObjectRevisions: [256] } + Component { + name: "QJSValue" + accessSemantics: "value" + } + Component { name: "varargs" accessSemantics: "value" -- cgit v1.2.3