aboutsummaryrefslogtreecommitdiffstats
path: root/src/checks/level0/README-fully-qualified-moc-types.md
diff options
context:
space:
mode:
Diffstat (limited to 'src/checks/level0/README-fully-qualified-moc-types.md')
-rw-r--r--src/checks/level0/README-fully-qualified-moc-types.md26
1 files changed, 0 insertions, 26 deletions
diff --git a/src/checks/level0/README-fully-qualified-moc-types.md b/src/checks/level0/README-fully-qualified-moc-types.md
deleted file mode 100644
index 43f34055..00000000
--- a/src/checks/level0/README-fully-qualified-moc-types.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# fully-qualified-moc-types
-
-Warns when a signal, slot or invokable declaration is not using fully-qualified type names, which will break old-style connects
-and interaction with QML.
-
-Also warns if a Q_PROPERTY of type gadget is not fully-qualified (Enums and QObjects in Q_PROPERTY don't need
-to be fully qualified).
-
-Example:
-
-namespace MyNameSpace {
-
- struct MyType { (...) };
-
- class MyObject : public QObject
- {
- Q_OBJECT
- Q_PROPERTY(MyGadget myprop READ myprop); // Wrong, needs namespace
- Q_SIGNALS:
- void mySignal(MyType); // Wrong
- void mySignal(MyNameSpace::MyType); // OK
- };
-}
-
-Beware that fixing these type names might break user code if they are connecting to them via old style connects,
-since the users might have worked around your bug and not included the namespace in their connect statement