Add type name to singleton (module api) implementations.

This change renames the previous module api implementation
to singleton types.

When a singleton type is registered, a type name must be provided
that is used when accessing the API from QML. This makes the
implementation more consistent with the rest of QML.

Task-number: QTBUG-26549
Change-Id: Iab0bb1ccf516bd3ae20aee562a64d22976e0aecd
Reviewed-by: Chris Adams <christopher.adams@nokia.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/tests/auto/qml/qqmlecmascript/data/handleReferenceManagement.dynprop.3.qml b/tests/auto/qml/qqmlecmascript/data/handleReferenceManagement.dynprop.3.qml
index 57fee6384b..6eaa54a8dc 100644
--- a/tests/auto/qml/qqmlecmascript/data/handleReferenceManagement.dynprop.3.qml
+++ b/tests/auto/qml/qqmlecmascript/data/handleReferenceManagement.dynprop.3.qml
@@ -16,13 +16,13 @@ Item {
         if (testProp == null) success = false;            // should not have triggered delete notify / zeroed testProp value
         if (testProp.variantCanary != 5) success = false; // should not have deleted vmemo of object referenced by testProp
         if (testProp.varCanary != 12) success = false;    // should not have collected vmemo vmeProperties
-        if (QObjectApi.qobjectTestWritableProperty != 42) success = false; // should not have been set to 43.
+        if (QObjectApi.QObject.qobjectTestWritableProperty != 42) success = false; // should not have been set to 43.
     }
 
     // then we manually delete the item being referenced
     function manuallyDelete() {
-        QObjectApi.deleteQObject(testProp);
-        if (QObjectApi.qobjectTestWritableProperty != 43) success = false; // should have been set to 43.
+        QObjectApi.QObject.deleteQObject(testProp);
+        if (QObjectApi.QObject.qobjectTestWritableProperty != 43) success = false; // should have been set to 43.
     }
 
     // after a gc (and deferred deletion process) the object should be gone