-
-
Notifications
You must be signed in to change notification settings - Fork 391
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
🐛 Check for new session first #1563
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
WalkthroughThis pull request changes how sessions are handled and migrated across authentication functions. In the Changes
Possibly related PRs
Poem
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
apps/web/src/auth/legacy/next-auth-cookie-migration.ts (1)
20-20
: Use optional chaining for safer cookie value access.The condition can be simplified and made safer using optional chaining.
- if (legacySessionCookie && legacySessionCookie.value) { + if (legacySessionCookie?.value) {🧰 Tools
🪛 Biome (1.9.4)
[error] 20-20: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
apps/web/src/auth/legacy/next-auth-cookie-migration.ts
(3 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
apps/web/src/auth/legacy/next-auth-cookie-migration.ts
[error] 20-20: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
⏰ Context from checks skipped due to timeout of 90000ms (4)
- GitHub Check: Unit tests
- GitHub Check: Linting
- GitHub Check: Integration tests
- GitHub Check: Type check
🔇 Additional comments (3)
apps/web/src/auth/legacy/next-auth-cookie-migration.ts (3)
5-5
: LGTM!The import of the
JWT
type is necessary for the new functions and is correctly placed.
49-62
: LGTM!The function follows best practices for cookie deletion by:
- Setting an expired date instead of direct deletion
- Including all necessary cookie attributes
- Checking for cookie existence before deletion
64-79
: Add validation for the secret password.The function implementation and refactoring look good, but consider adding validation for the secret password.
async function setNewSessionCookie(res: NextResponse, jwt: JWT) { + if (!process.env.SECRET_PASSWORD) { + throw new Error("SECRET_PASSWORD is not configured"); + } + const newJWT = await encode({ token: jwt, secret: process.env.SECRET_PASSWORD, salt: newCookieName, });Also applies to: 88-89
Summary by CodeRabbit