Refactor vite to nextjs for ability to adapt profile data on server#87
Open
oliCHECK24 wants to merge 5 commits intothtauhid:mainfrom
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@oliCHECK24 is attempting to deploy a commit to the thtauhid's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Task Overview
The main objective of this task was to create a user-friendly GUI for editing profile data. This involved refactoring the existing Vite application to a Next.js framework to facilitate the creation of APIs that can manage user data effectively.
Reason for Refactoring to Next.js
The refactor from Vite to Next.js was essential for several reasons:
API Route Support: Next.js provides built-in support for API routes, allowing the creation of serverless functions directly within the application. This capability is crucial for handling data operations (such as create, read, update, and delete) seamlessly on the server, enabling efficient data management without the need for an additional backend service.
Server-Side Rendering: Next.js offers server-side rendering (SSR) out of the box, which enhances the performance and SEO of the application. This is particularly beneficial for profile editing, as it ensures that user data is rendered on the server before being sent to the client, resulting in faster load times and better user experience.
Improved Project Structure: The Next.js framework enforces a clear project structure that promotes best practices, making it easier to manage and scale the application. It allows for organized code separation between the client and server logic, which improves maintainability.
Enhanced Features: By transitioning to Next.js, we gain access to additional features like automatic code splitting, image optimization, and built-in routing, which contribute to a more robust and performant application.
Changes Made
Refactored Application:
Developed GUI for User Data Management:
/edit./edit/[username].Key Features
URLs
/edit/edit/[username]