-
-
Notifications
You must be signed in to change notification settings - Fork 675
implement collaboration upgrade proposals #1856
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
35879aa
implement collaboration upgrade proposals (invite roles, identity, du…
HarshShinde0 acf9808
style: auto-format (ruff + oxfmt) [pre-commit.ci]
pre-commit-ci[bot] ae9217f
fix: address review fixes
HarshShinde0 4956a36
style: auto-format (ruff + oxfmt) [pre-commit.ci]
pre-commit-ci[bot] b1f9e7b
fixes
HarshShinde0 43cb3d3
style: auto-format (ruff + oxfmt) [pre-commit.ci]
pre-commit-ci[bot] 7e1e8e6
fix(collab): update rate-limit cleanup, proxy IP handling, and collab…
HarshShinde0 61b5cf2
style: auto-format (ruff + oxfmt) [pre-commit.ci]
pre-commit-ci[bot] 6d39e33
fix(collab): defer invite consumption until after join authorization …
HarshShinde0 5238173
fix(collab): enforce provider string type safety, guard host invites,…
HarshShinde0 23b20ff
style: auto-format (ruff + oxfmt) [pre-commit.ci]
pre-commit-ci[bot] 553258c
Merge branch 'main' into feat/collab-upgrade
giswqs 1757525
Address Claude review feedback
giswqs a203d5f
Address Claude review feedback
giswqs c8fc3e1
feat(collab): add proactive layer locking UI feedback and host controls
HarshShinde0 4cf136d
style: auto-format (ruff + oxfmt) [pre-commit.ci]
pre-commit-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Minor UX note: this PR adds several new join-rejection reasons the relay can send back (
identity-required,forbiddenfor a blocked participant key), each with a specificmessagestring (e.g. "You have been blocked from this session by the host.", "Sign-in required to join this session.").api.joinnow rejects withnew Error(message.message)carrying that specific text (see the newpendingConnectRefhandling inuseCollaboration.ts), but this catch block discards it in favor of the generict("collaborate.connectFailed"). A user who gets blocked or hits an identity gate sees the same "connection failed" message as a plain wrong invite code, with no way to tell why.This pattern predates this PR (the removed comment even called it out as intentional), so it may be out of scope — but the set of distinguishable failure reasons has grown meaningfully with this feature, which makes surfacing
err.message(or at least distinguishing "blocked"/"identity-required" specifically) more valuable than it was before.Confidence: low-medium.