feat(deeplink): unify links - #334
Merged
Merged
Conversation
Emailed auth links leaked the API route shape (/api/auth/verify) and invites used the cryptic /j/. Public links now read /verify/<token>, /reset-password/<token>, /join/<token>; /open is unchanged. All three token routes carry the token as a path segment via pathSuffixParam. Manifest prefixes keep the trailing slash, so a tokenless /verify is not claimed. Old paths are dropped outright — no aliases. The /api/auth/* endpoints the app POSTs to are untouched; only the link the user clicks moves. Backend must emit the new paths, or in-flight emails and already-shared invites lose their token.
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.
Emailed auth links leaked the API route shape (/api/auth/verify) and invites used the cryptic /j/. Public links now read /verify/, /reset-password/, /join/; /open is unchanged. All three token routes carry the token as a path segment via pathSuffixParam.
Manifest prefixes keep the trailing slash, so a tokenless /verify is not claimed. Old paths are dropped outright — no aliases.
The /api/auth/* endpoints the app POSTs to are untouched; only the link the user clicks moves. Backend must emit the new paths, or in-flight emails and already-shared invites lose their token.