feat: Add User DAO #676
feat: Add User DAO #676
Conversation
This change introduces a Data Access Object (DAO) for the User model. This is the first step in a larger effort to abstract the database layer and eventually migrate to PostgreSQL. The new UserDAO encapsulates all database interactions for the User model, and the GraphQL logic for users has been refactored to use this new DAO. Unit tests for the DAO have also been added.
|
👋 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 For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This change introduces a Data Access Object (DAO) for the User model. This is the first step in a larger effort to abstract the database layer and eventually migrate to PostgreSQL. The new UserDAO encapsulates all database interactions for the User model, and the GraphQL logic for users has been refactored to use this new DAO. Unit tests for the DAO have also been added.
PR created automatically by Jules for task 1283899384026071408 started by @rajat1saxena