Backend: Implemented Profile Data & Calendar Journals#1
Open
ananyavarshney1 wants to merge 1 commit into
Open
Conversation
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
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.
🚀 Overview
This PR implements the backend required for the user Profile Page and the Calendar Journal interaction using Dart Frog and Supabase.
🛠 Changes Made
_middleware.dart: Added a global Supabase provider. Configured to use the.envfile architecture to securely hold theservice_rolekey (bypassing RLS securely for the backend).GET /profile: Created an endpoint that accepts auserIdquery parameter and fetches the user's currentstreakandseedsfrom theuserstable.GET /profile/journal: Created an endpoint that accepts auserIdanddate. It queries thejournal_entriestable and returns a JSON list of all journals for that specific day, including thesummary_text,initial_mood, andfinal_mood.🧪 Testing Notes for the Team
To make frontend development and testing easier, authentication checks are currently bypassed on these profile routes.
🔒 Security Note
SUPABASE_SERVICE_ROLE_KEYhas been moved to a local.envfile and added to.gitignore. Whoever pulls this branch will need to create their own.envfile in thebackend/folder to run the server.