Allow to share RichObjects to chats

[nickvergessen]

Sample request:

curl -k https://localhost/ocs/v2.php/apps/spreed/api/v1/chat/XXXXX/share \
    -u admin:admin \
    -H "OCS-ApiRequest: true" \
    -d 'objectType=deck-card'\
    -d 'objectId=9'\
    -d 'metaData={"type":"deck-card","id":"9","name":"Card title","boardname":"Board name","stackname":"Stack name","link":"https:\/\/nextcloud21.local\/index.php\/apps\/deck\/#\/board\/2\/card\/9"}'

As per discussion in the chat, for now it is "garbage-in garbage-out". The resolution for that is extending the rich-object part in the server to allow to "parse"/"verify" data by each app even allowing them to return "Not accessible" or something alike as currently hard coded for files.

• Allow posting rich-object
• Parse rich-objects
• Add test
• Add integration test
• Add documentation
• Add capability

[nickvergessen]

Documented, tests added and capability added for clients.

[PVince81]

Code looks fine, see minor comments.

[PVince81]

@nickvergessen One question also while grepping for {file} I saw that there was a special handling in Quote.vue, is that one necessary also for {object} ?

[marcoambrosini]

does what it says!

[nickvergessen]

One question also while grepping for {file} I saw that there was a special handling in Quote.vue, is that one necessary also for {object} ?

That's to show the preview instead of the file name. For now the card name is good enough. When we improve styling of deck cards we can revisit this.

[marcoambrosini]

Blocking while finishing to style the card component

[nickvergessen]

Rebased

[nickvergessen]

/backport to stable21.1

[nickvergessen]

/backport to stable21.1

[backportbot-nextcloud]

The backport to stable21.1 failed. Please do this backport manually.