Group related endpoints in Swagger documentation to increase the experience of the developer #710
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
medium priority
ux
Description
Currently, our API documentation using Swagger is not very developer friendly, especially when looking for an endpoint. Endpoints that pertain to a particular entity should be grouped together so that if a developer wants to use endpoints that have to do with projects, they could refer to the Project section on the API documentation and find all the endpoints that have something to do with projects. Same thing for Authentication and the rest.
Currently we have
We could change to
The text was updated successfully, but these errors were encountered: