Stub for akonadi configuration.

Instead of dealing with dedicated configuration facades,
we'll integrate that directly into the domain interface. That way it should
be rather natural for applications to i.e. query for available resources,
and then configure them in the same way some other domain object would be
modified.

1 files changed, 6 insertions, 0 deletions

diff --git a/common/clientapi.cpp b/common/clientapi.cpp
index 48de1b0..c6f5582 100644
--- a/common/clientapi.cpp
+++ b/common/clientapi.cpp
@@ -29,6 +29,12 @@ QByteArray getTypeName<Todo>()
     return "todo";
 }
 
+template<>
+QByteArray getTypeName<AkonadiResource>()
+{
+    return "akonadiresource";
+}
+
 } // namespace Domain
 
 void Store::shutdown(const QByteArray &identifier)