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.
Implemented another approach to To do list application - ensures user engagement is higher than a simple app. Added an interactive User Interface, users can add, update or delete a task if they are only logged in. Also created an AI Kitchen Assistant to generate a cooking tasks list for user engagement.
Approaches to creating the To do list fullstack application:
Authentication is handled by Google OAuth for fast shipping of auth.
Data persistence is from Supabase since they have a generous free tier.
Supabase SSR for server side data fetching.
API routes for client side data handling.
Used the Prisma's built in model system for type safety across multiple data usages.
Implemented Row Level Security from Supabase to ensure safety of the data.
Created a separate Services ts file for code organization.
Making sure to always apply "DRY" (Don't Repeat Yourself) for a clean codebase and abstracted data handling.
Created a service layer: The Axios → Service → Model Flow:
1. Axios grabs the raw data from the API.
2. The Service layer catches that response and deconstructs it.
3. I map that data directly to my Prisma models.