Feat/user settings capability #2655
Conversation
| "settings": []map[string]interface{}{ | ||
| { | ||
| "enabled": true, | ||
| "version": "1.0.0", | ||
| }, | ||
| }, |
There was a problem hiding this comment.
That's just the oCIS side of capabilities. It is only used to configure REVA. Therefore to actually have it available on the endpoint you also need to add this to REVA. You can see in this PR how do that: https://github.com/cs3org/reva/pull/2088/files
Currently curl -k 'https://localhost:9200/ocs/v1.php/cloud/capabilities?format=json' -u einstein:relativity | jq . does only give me:
"user": {
"send_mail": true,
"profile_picture": false
}
There was a problem hiding this comment.
Okay interesting, I thought we're wrapping/extending REVA's capabilities in oCIS...will add a PR there then, too
|
Depends on cs3org/reva#2189 to be merged |
wkloucek
force-pushed
the
feat/user-settings-capability
branch
from
c493700 to
f30b5af
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
Description
In the web client, requests for the oCIS settings service are currently also being sent to OC10 backends. With this capability, we can make sure only to send such requests if the right service is present in the backend. Potentially, this capability could also be used by other clients to check availability of settings endpoints to e.g. handle user settings on mobile
Related Issue
Types of changes