As a developer, I would like accurate documentation of my API as well as the documentation system being easy to edit, so I am more confident in the behavior of the API and am easily able to add changes to the documentation when the API gets changes.
Acceptance criteria
[ ] A documentation system that is easy to use should be implemented
[ ] All routes should be 100% covered by the documentation
create-issue-branch[bot]
commented
2 years ago
Project/Library/Tool (or repo) specific
MealPlanr
Priority
MAJOR
Description
As a developer, I would like accurate documentation of my API as well as the documentation system being easy to edit, so I am more confident in the behavior of the API and am easily able to add changes to the documentation when the API gets changes.
Acceptance criteria
Comments / questions
https://tsoa-community.github.io/docs/getting-started.html
https://medium.com/@gavinhaynes_58103/how-to-add-a-swagger-ui-to-a-ts-expressjs-app-using-tsoa-573a2235083
Code of Conduct