potential problem if two QML modules have class with the same name

There is big potential problem in scenarios where two QML modules contain  classes with the same name, even if they are in different namespaces. When these classes are exposed to QML and the generated C++ code from the QML compiler (qmlsc) includes those types, it might not properly handle the namespace qualification, leading to ambiguities or incorrect type resolution.

In above scenario when these types are imported into QML. then the generated qmlsc c++ will simply #include <TheType.h> without a qualifying path and will also not use the given namespace. Therefore the compiler can fail if the "assumed" type is in fact the wrong one.

So if generated code some how can use library path or namespace then it would be great.