refac: review and refactor API #428
Draft
Conversation
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
fishonamos
changed the title
fishonamos
changed the title
Member
|
Ah nice , looking forward |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 pr will review and refactor the existing API code located within the backend folder and improve the overall structure, removing unused and redundant code.
The codebase will be modularized for better maintainability and readability. Additionally, I will fix the Swagger documentation to ensure accurate rendering of all endpoints and update docstrings across the API for improved clarity.
These changes also aim to enhance system performance, scalability and set a cleaner foundation for future development.
Closes #415