Add duplicate name handling, participant populate, and auth error improvements#74
Open
Add duplicate name handling, participant populate, and auth error improvements#74
Conversation
…r improvements - Allow duplicate participant names by appending random #XXX suffix on collision instead of blocking with 409 error (both guest and authenticated join flows) - Return populated participantIds (name, userId) in GET /users/:userId/events to enable frontend participant connection loading - Return LinkedIn-specific error message when a LinkedIn user tries local signup - Update all relevant docs (API reference, schema, realtime guide, roadmap)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
#XXXrandom suffix (e.g.,John#472). Applies to both guest and authenticated join flows.GET /api/users/:userId/eventsnow returns populatedparticipantIds(withnameanduserId) for each event, enabling the frontend to load participant connections.