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, 9 insertions, 3 deletions

diff --git a/common/resource.cpp b/common/resource.cpp
index 533a132..32a92ca 100644
--- a/common/resource.cpp
+++ b/common/resource.cpp
@@ -55,19 +55,20 @@ void Resource::setLowerBoundRevision(qint64 revision)
 class ResourceFactory::Private
 {
 public:
+    QByteArrayList capabilities;
     static QHash<QString, QPointer<ResourceFactory>> s_loadedFactories;
 };
 
 QHash<QString, QPointer<ResourceFactory>> ResourceFactory::Private::s_loadedFactories;
 
-ResourceFactory::ResourceFactory(QObject *parent) : QObject(parent), d(0)
+ResourceFactory::ResourceFactory(QObject *parent, const QByteArrayList &capabilities) : QObject(parent), d(new ResourceFactory::Private)
 {
-    Q_UNUSED(d);
+    d->capabilities = capabilities;
 }
 
 ResourceFactory::~ResourceFactory()
 {
-    // delete d;
+    delete d;
 }
 
 ResourceFactory *ResourceFactory::load(const QByteArray &resourceName)
@@ -117,6 +118,11 @@ ResourceFactory *ResourceFactory::load(const QByteArray &resourceName)
     return nullptr;
 }
 
+QByteArrayList ResourceFactory::capabilities() const
+{
+    return d->capabilities;
+}
+
 } // namespace Sink
 
 // Ignore warning I don't know how to fix in a moc file