QQmlJSImportsVisitor: Break inheritance cycles

If we keep them around, later passes on the same data may run into
infinite loops. We cannot fully prevent any further processing of the
data because the import can happen from deep within a hierarchy of
components and modules.

Also, separate the deprecation check from the inheritance check.

Pick-to: 6.2
Change-Id: I62ce7cd15be83f60cd72b63ab858632fbc7dea66
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

1 files changed, 7 insertions, 0 deletions

diff --git a/tests/auto/qml/qmlcppcodegen/data/Cycle1.qml b/tests/auto/qml/qmlcppcodegen/data/Cycle1.qml
new file mode 100644
index 0000000000..66784f25f4
--- /dev/null
+++ b/tests/auto/qml/qmlcppcodegen/data/Cycle1.qml
@@ -0,0 +1,7 @@
+import QtQml 2.0
+Cycle2 {
+    id: itt
+    QtObject {
+        property var thing: itt
+    }
+}