Migration from Next.js to NestJS and TRPC to RESTful API#3
Merged
Conversation
ayequill
approved these changes
Mar 23, 2024
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.
This pull request contains significant changes to our application's backend and data model. Here's a summary of what has been done:
Backend Migration: We've migrated our backend from Next.js to NestJS. This change will allow us to leverage the robustness and flexibility of NestJS, improving our application's performance and scalability.
API Transition: We've transitioned from using tRPC to a RESTful API. This change simplifies our API structure and makes it more accessible and standardized.
Authentication Update: We've moved from NextAuth to Clerk for authentication. Clerk provides a more secure and comprehensive solution for user management and authentication.
Data Model and Prisma Schema Improvement: We've made significant improvements to our data model and Prisma schema. These changes optimize our database interactions and make our data handling more efficient.
Clerk Demo: We've created a demo using React.js to showcase how Clerk can be integrated into our application for user authentication.