Update the stored space object after members have been changed #6545
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: