Fix: read/write access control for public repos #115
Merged
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.
For a public repo, even an anonymous user can read everything in it, but only the owner and collaborators are allowed to edit. In this PR: we further distinguish the access for different roles in a repo, enforced the access rule both on the front-end and back-end side.
Besides, remove the awareness info (remote cursor/selection) of guests, only show the operation update from an owner/collaborator. A guest can never edit/run code in the pod or drag a pod.
Now, a public repo can also be shared with collaborators.
TODO