Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation to include all API endpoints #20

Open
demilolu opened this issue Sep 21, 2021 · 5 comments
Open

Update documentation to include all API endpoints #20

demilolu opened this issue Sep 21, 2021 · 5 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request hacktoberfest stale

Comments

@demilolu
Copy link
Contributor

Background on the problem the feature will solve/improved user experience

The TakeTwo-WebAPI documentation seems to require users to first successfully run the API locally before being able to know what the full endpoints are for the API as listed here

Review the TakeTwo OpenAPI documentation

For an overview of the available endpoints navigate to http://localhost:8000/docs

The dataset is listed in the documentation, but the full API documentation should be in the read.me itself.

Describe the solution you'd like

Update documentation to provide full documentation on API withouth requiring user to get WebAPI running locally.

Tasks

Description of the development tasks needed to complete this issue, including tests,

Acceptance Criteria

Standards we believe this issue must reach to be considered complete and ready for a pull request. E.g precisely all the user should be able to do with this update, performance requirements, security requirements, etc as appropriate.

@demilolu demilolu added documentation Improvements or additions to documentation hacktoberfest labels Sep 21, 2021
@github-actions
Copy link

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed in 14 days.

@github-actions github-actions bot added the stale label Oct 24, 2021
@github-actions github-actions bot closed this as completed Nov 7, 2021
@naagma5 naagma5 removed the stale label Nov 18, 2021
@naagma5 naagma5 reopened this Nov 18, 2021
@github-actions
Copy link

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed in 14 days.

@github-actions github-actions bot added the stale label Dec 19, 2021
@github-actions github-actions bot closed this as completed Jan 3, 2022
@demilolu demilolu reopened this Feb 3, 2022
@demilolu demilolu removed the stale label Feb 3, 2022
@github-actions
Copy link

github-actions bot commented Apr 5, 2022

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed in 14 days.

@github-actions github-actions bot added the stale label Apr 5, 2022
@upkarlidder
Copy link
Member

Possible solution is to create a GitHub action that generates the swagger docs on every PR merge into main. The docs be hosted as github pages on this repo.

@upkarlidder upkarlidder added enhancement New feature or request and removed stale labels May 5, 2022
@github-actions
Copy link

github-actions bot commented Jul 5, 2022

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed in 14 days.

@github-actions github-actions bot added the stale label Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request hacktoberfest stale
Projects
None yet
Development

No branches or pull requests

3 participants