-
Notifications
You must be signed in to change notification settings - Fork 4
feat: add authentication feature #27
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
Conversation
|
@samthelightbender is attempting to deploy a commit to the sensasidelight's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sensasi-delight
left a comment
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.
|
fixed lint error, please check again 🚀 |
Changed the Prisma schema path in all related npm scripts from 'src/prisma/schema.prisma' to 'prisma/schema.prisma' to reflect the new schema location.
Centralizes the Prisma schema path within `prisma.config.ts`, enabling the removal of redundant `--schema` arguments from database-related npm scripts. Integrates `prisma format` into the `lint` and `lint:fix` commands to ensure consistent code formatting. Removes the unused `eslint-plugin-naming` dependency and cleans up an unused `lucide-react` import and unutilized `ctx` parameters in authentication callbacks.
Temporarily comments out models and fields unrelated to core authentication. This includes `Post`, `Like`, `Comment`, `Report`, `Follow`, and `LeaderboardSnapshot` models, along with their associated relations in the `User` model. This change streamlines the database schema to focus solely on the initial authentication functionality, enabling a clearer development path. These features will be uncommented and implemented as they are developed. Also renames the base migration file to accurately reflect its purpose in setting up the initial authentication tables.
This commit adds support for authenticating with Google and GitHub in addition to the existing authentication mechanism. This enhancement allows users to login using their social media accounts, providing a more convenient and secure experience. The changes include adding new environment variables and registering the authentication routes.
sensasi-delight
left a comment
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.
- add sign up form
- show error auth to frontend
|
see the otp code at the verification table manually (for temporary) |
|
Read Resend SMTP Docs and put the Resend API Key to your development env |
Enhances the accessibility and readability of the login form by providing clear labels and links for users. Updates the layout to direct users to the correct authentication routes. Adds social login buttons for GitHub. Updates the CTAs on the landing page and header to direct users to the login/auth/register pages. Improves overall user navigation and reduces confusion.

feat: Add Login (Email and Password) and Logout Functionality
Description
This pull request introduces the initial phase of the authentication feature, focusing specifically on login and logout functionality. It lays the groundwork for the complete authentication system by setting up the necessary database models and a seeding script for test users.
Key Changes:
SessionandVerificationmodels to the Prisma schema to support authentication.Setup and Testing Instructions
To get this feature running locally, please follow these steps in order:
Add Environment Variables
Make sure you add the following to your
.env.development.examplefile.Generate Prisma Client
Run this command to generate the Prisma Client according to the latest schema.
Run Database Migrations
This command will apply the new schema changes to your database.
Seed the Database
Use this command to populate the database with initial user data for testing purposes.
After completing these steps, the application will be ready for testing the login and logout features.