Problem statement
AuthRoutes currently uses a mix of naming styles:
/passKeyLogin/verifyPhoneOTP/verifyEmailOTP/registerPasskey/magiclinks-sent/verify-magiclink
This makes the built-in route surface harder to remember, document, and explain.
Goal
Move the built-in routes toward a consistent naming convention, ideally kebab-case, while preserving compatibility for existing adopters.
Proposed solution
Acceptance criteria
AuthRoutes supports a consistent canonical route set- Current legacy route names continue to work during migration
- README lists the canonical routes
- Tests cover both canonical routes and legacy aliases where appropriate
Alternatives considered
No response
Problem statement
AuthRoutescurrently uses a mix of naming styles:/passKeyLogin/verifyPhoneOTP/verifyEmailOTP/registerPasskey/magiclinks-sent/verify-magiclinkThis makes the built-in route surface harder to remember, document, and explain.
Goal
Move the built-in routes toward a consistent naming convention, ideally kebab-case, while preserving compatibility for existing adopters.
Proposed solution
Acceptance criteria
AuthRoutessupports a consistent canonical route setAlternatives considered
No response