Don't set capabilities as property on creation.

Instead we make it part of the plugin.
This ensure we also have access to the proper capabilities when creating
a resource via sinksh.

1 files changed, 7 insertions, 3 deletions

diff --git a/examples/maildirresource/maildirresource.cpp b/examples/maildirresource/maildirresource.cpp
index 6a03263..997ddef 100644
--- a/examples/maildirresource/maildirresource.cpp
+++ b/examples/maildirresource/maildirresource.cpp
@@ -570,9 +570,14 @@ MaildirResource::MaildirResource(const Sink::ResourceContext &resourceContext)
 
 
 MaildirResourceFactory::MaildirResourceFactory(QObject *parent)
-    : Sink::ResourceFactory(parent)
+    : Sink::ResourceFactory(parent,
+            {Sink::ApplicationDomain::ResourceCapabilities::Mail::storage,
+            Sink::ApplicationDomain::ResourceCapabilities::Mail::drafts,
+            "-folder.rename",
+            Sink::ApplicationDomain::ResourceCapabilities::Mail::trash,
+            Sink::ApplicationDomain::ResourceCapabilities::Mail::sent}
+            )
 {
-
 }
 
 Sink::Resource *MaildirResourceFactory::createResource(const ResourceContext &context)
@@ -596,4 +601,3 @@ void MaildirResourceFactory::removeDataFromDisk(const QByteArray &instanceIdenti
 {
     MaildirResource::removeFromDisk(instanceIdentifier);
 }
-