🧪 test: improve coverage for safeGetSession in hooks.server.ts - #91
🧪 test: improve coverage for safeGetSession in hooks.server.ts#91Sparkier wants to merge 2 commits into
Conversation
Co-authored-by: Sparkier <5690524+Sparkier@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Co-authored-by: Sparkier <5690524+Sparkier@users.noreply.github.com>
🎯 What: Added tests for the
safeGetSessionfunction within thesupabasemiddleware insrc/hooks.server.tsto explicitly handle the edge case wheregetSessionsucceeds butgetUserfails, indicating an invalid JWT token. To enable this, thesupabasehandler function was exported for testability.📊 Coverage:
session: null, user: nullis returned whengetSessionfinds no session.session: null, user: nullis returned whengetSessionsuccessfully retrieves a session butgetUserthrows an error (JWT invalidation).getSessionandgetUsersucceed.✨ Result: Enhanced test reliability and coverage, ensuring that unauthenticated access scenarios are properly verified and protected against future regressions.
PR created automatically by Jules for task 826373049521642647 started by @Sparkier