-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the stored space object after members have been changed #6545
Conversation
Results for oCISFiles1 https://drone.owncloud.com/owncloud/web/23351/55/1
|
Results for oCISTrashbinUploadMoveJourney https://drone.owncloud.com/owncloud/web/23351/69/1
|
bf3f535
to
2139646
Compare
2139646
to
2b3041d
Compare
Results for oCISTrashbinUploadMoveJourney https://drone.owncloud.com/owncloud/web/23362/69/1
|
Results for oCISSharingPublic1 https://drone.owncloud.com/owncloud/web/23362/67/1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳
Kudos, SonarCloud Quality Gate passed! |
Results for oCISSharingAndUpload https://drone.owncloud.com/owncloud/web/23365/66/1
|
Description
We now update the stored space after its members have been changed. Also, the permission-object of a built space has been simplified in the course of this.
Currently the only way to update the space object is by fetching the space again because the response from the OCS-API gives us no usable information. As soon as UUIDs have been introduced to the OCS-API, we could use those instead.
Note that there is still a caching bug in OCIS. E.g. when navigating between space's share panels via the share indicator, and adding/removing members, and then switching back and forth between the share panels again, the change seems to be lost. A reload reveals that this is actually not the case.
Related Issue
Types of changes
Checklist: