Fix Unsharing Workspace
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Describe the bug
When I share a running workspace with a colleague and then stop the sharing he still is able to write to my workspace until he refreshes the window. He is not actively kicked from my workspace as I would have expected
To Reproduce
- Create Workspace
- Share Workspace
- Let other user connect to workspace
- Unshare workspace
- Other user is still able to change content
Expected behavior
I would have the other user expected to be kicked from my workspace. At least he should not be able to change the content any more after I unshared the workspace.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the shared-workspace flow: connect a second user, unshare the workspace, and verify whether that user can still edit. Trace the workspace sharing and connection-handling entry points involved in unsharing. Done means the other user is disconnected or immediately loses write access without needing to refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100