Refactor - backend code refactored #8
Merged
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 introduces a complete refont of backend and foundational setup and documentation improvements for the backend of the TaskFlow platform. The most important changes include adding a comprehensive backend README, introducing code formatting standards, updating
.gitignorefor best practices, and removing unused configuration and Docker files.Backend teck stack:
Switched from Fastify to NestJS powered by Fastify to add abstraction into the API
Documentation and Project Setup:
backend/README.mddescribing the architecture, tech stack, setup instructions, and project structure for the TaskFlow API.Code Formatting and Configuration:
.prettierrcfiles to both the root and backend directories to enforce consistent code formatting standards across the project. [1] [2]Repository Hygiene:
backend/.gitignoreto exclude build output, logs, IDE configs, environment files, and other common artifacts, improving repository cleanliness.Configuration Cleanup:
backend/.env.templatefile, likely in favor of direct.envsetup instructions in the README.Docker and Build System:
backend/Dockerfile, indicating a shift away from the previous Node.js Docker setup or a transition to a new deployment strategy.