fix: supabase ssr bug

[gaboesquivel]

Summary by CodeRabbit

• New Features
  • Enhanced user data fetching and authentication across the app using a new method for better reliability and security.
• Improvements
  • Improved error handling for scenarios where user or user email is not found, ensuring a smoother user experience.
• Refactor
  • Updated various components and services to utilize a more efficient method for user data retrieval and authentication.
• Chores
  • Reorganized exports in the Supabase service for better maintainability and clarity.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
masterbots	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 8, 2024 7:56pm

[coderabbitai]

Walkthrough

The recent updates across the MasterBots.ai platform focus on enhancing user data fetching and authentication processes. A new method, createSupabaseServerClient, has been introduced to streamline interactions with Supabase, replacing the older getUserProfile. This shift aims to improve error handling, especially concerning user or email verifications, and ensures a smoother experience in user profile management and thread retrieval across various components.

Changes

File Path	Change Summary
apps/.../[chatbot]/[threadId]/page.tsx apps/.../[chatbot]/page.tsx apps/.../c/page.tsx apps/.../components/layout/header.tsx	Updated to use createSupabaseServerClient for data fetching and getUser for authentication. Enhanced error handling for user/email not found.
apps/.../services/supabase/index.ts	Reorganized exports, including renaming files and adjusting export statements.

🐇✨
In the world of code, where changes bound,
A rabbit hopped, leaving marks profound.
With a flick and a hop, Supabase in sight,
createSupabaseServerClient takes flight.
Errors quiver, as checks now tight,
A smoother flow, into the night. 🌙
🌟🐾

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?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

⚡️ Lighthouse report

Page: https://masterbots-1jjx4x30m-bitcash.vercel.app/
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712606171626-22751.report.html

Category	Score
🟢 Performance	92
🟢 Accessibility	93
🟢 Best practices	100
🟠 SEO	67
🔴 PWA	38

Page: https://masterbots-1jjx4x30m-bitcash.vercel.app/b/moneybot
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712606172061-7404.report.html

Category	Score
🟢 Performance	90
🟢 Accessibility	93
🟢 Best practices	100
🟠 SEO	67
🔴 PWA	38

Page: https://masterbots-1jjx4x30m-bitcash.vercel.app/u/slug-1
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712606172421-84101.report.html

Category	Score
🟢 Performance	92
🟢 Accessibility	93
🟢 Best practices	100
🟠 SEO	67
🔴 PWA	38

Page: https://masterbots-1jjx4x30m-bitcash.vercel.app/p
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712606172798-25384.report.html

Category	Score
🟢 Performance	91
🟢 Accessibility	93
🟢 Best practices	100
🟠 SEO	67
🔴 PWA	38

Page: https://masterbots-1jjx4x30m-bitcash.vercel.app/health
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712606173236-5065.report.html

Category	Score
🟢 Performance	93
🟢 Accessibility	93
🟢 Best practices	100
🟠 SEO	67
🔴 PWA	38

Page: https://masterbots-1jjx4x30m-bitcash.vercel.app/health/a8103808-14a3-48ed-aa5a-9e490cfdcf0e
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712606173843-44253.report.html

Category	Score
🟢 Performance	91
🟢 Accessibility	93
🟢 Best practices	100
🟠 SEO	67
🔴 PWA	38

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b1afa77 and 9cc4fb3.

Files selected for processing (5)

• apps/masterbots.ai/app/c/[chatbot]/[threadId]/page.tsx (1 hunks)
• apps/masterbots.ai/app/c/[chatbot]/page.tsx (3 hunks)
• apps/masterbots.ai/app/c/page.tsx (1 hunks)
• apps/masterbots.ai/components/layout/header.tsx (1 hunks)
• apps/masterbots.ai/services/supabase/index.ts (1 hunks)

Additional comments not posted (7)

apps/masterbots.ai/services/supabase/index.ts (1)

1-2: Ensure all references to the renamed exports (./client and ./supa-server-client) are updated across the application to maintain consistency and prevent import errors.

Verification successful

---

The executed script aimed to verify if all references to the old export paths (supa-browser-client and supa-server.service) were updated, as indicated by the changes in the index.ts file within the Supabase service directory. The script did not produce any output, which suggests that there are no lingering references to these old paths in TypeScript files within the codebase. This implies that the renaming and adjustments in export statements, as seen in the provided code snippet, are consistent and should not lead to import errors due to unresolved references to the old export paths.

Given the absence of output from the script, it can be inferred that the necessary updates across the application have been made to accommodate the changes in export paths. Therefore, the review comment concerning the need to ensure all references to the renamed exports are updated across the application appears to have been addressed satisfactorily.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Verify that all references to the old export paths are updated.
rg --type ts "supa-browser-client|supa-server.service"

Length of output: 56

apps/masterbots.ai/app/c/page.tsx (2)

10-20: The implementation of createSupabaseServerClient and user data retrieval using getUser appears correct. However, consider adding more detailed error messages to distinguish between "user not found" and "user email not found" scenarios for improved debugging and user feedback.

---

29-29: Ensure that the userId passed to getThreads is correctly obtained from the dbUserProfile. This change is crucial for maintaining the integrity of thread retrieval based on user identity.

apps/masterbots.ai/components/layout/header.tsx (1)

15-19: The use of createSupabaseServerClient for fetching user data is correctly implemented. Consider adding null checks for cookies().get('hasuraJwt') before accessing its value to prevent potential runtime errors.

apps/masterbots.ai/app/c/[chatbot]/[threadId]/page.tsx (1)

10-15: The transition to createSupabaseServerClient for user data retrieval is correctly implemented. Ensure that error handling for user or user email not found is adequately tested to provide a smooth user experience.

apps/masterbots.ai/app/c/[chatbot]/page.tsx (2)

19-29: The modifications to the user authentication flow using createSupabaseServerClient and subsequent user profile retrieval are correctly implemented. Consider implementing a fallback or retry mechanism for transient network errors during user profile retrieval to enhance robustness.

---

45-45: Correctly passing the userId from the userProfile to getThreads ensures that thread retrieval is accurately scoped to the authenticated user. This is a critical update for user data integrity.