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

API Documentation #1

Open
navinpai opened this issue Oct 1, 2022 · 12 comments
Open

API Documentation #1

navinpai opened this issue Oct 1, 2022 · 12 comments
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers help wanted Extra attention is needed

Comments

@navinpai
Copy link
Member

navinpai commented Oct 1, 2022

Document the SlashGo Server API in either README or in a more in-depth format like OpenAPI to allow easy reference to API methods, fields and possible edge cases.

@navinpai navinpai added documentation Improvements or additions to documentation good first issue Good for newcomers help wanted Extra attention is needed labels Oct 1, 2022
@zahertalab
Copy link

Is it a RESTful API? If yes, where I can start?

@navinpai
Copy link
Member Author

navinpai commented Oct 2, 2022

Hey @zahertalab ,

Yes, it is a restful API. The API routes are all part of the api directory and they call code in the controllers directory which can be used as a reference for validations etc.

@zahertalab
Copy link

I wonder if there is some swagger or open API UI available?

@navinpai
Copy link
Member Author

navinpai commented Oct 10, 2022

We don't have Swagger/OpenAPI set up as of today, but if you can set up a swagger yaml, I'd be happy to have it part of the project to make it more accessible to folks in the future! 👍

Update: @zahertalab We now have a new swagger documentation repo: https://github.com/Slash-Go/Docs ... I've moved the issue to the new repo. Docs are currently served at https://docs.slashgo.link/ from this repo.

@navinpai navinpai transferred this issue from Slash-Go/SlashGoServer Oct 13, 2022
@EleekaN
Copy link

EleekaN commented Oct 31, 2022

Hi @navinpai I want to work on this. Just to summarize, you want the swagger documentation to be updated with other end points like Auth , Organizations etc.

@navinpai
Copy link
Member Author

Hi @navinpai I want to work on this. Just to summarize, you want the swagger documentation to be updated with other end points like Auth , Organizations etc.

Yes, that's right... It would be great to have the swagger.yaml updated with all the endpoints and responses

Thanks in advance!

@EleekaN
Copy link

EleekaN commented Oct 31, 2022 via email

@navinpai
Copy link
Member Author

Sure...is there one location/file where I can get all the endpoints and responses. I remember seeing some of it on different folders.

The API routes are all part of the api directory and they call code in the controllers directory which can be used as a reference for validations etc. Sorry we don't have a single path for it yet, but we're hoping this repo becomes that single source of truth for the API 😸

@EleekaN
Copy link

EleekaN commented Nov 2, 2022

localhost://3000 doesn't reflect the changes I make on the swagger.yaml file. How can I sync it locally, so I can validate my work?

@navinpai
Copy link
Member Author

navinpai commented Nov 2, 2022

Once you make changes in swagger file, please do the following steps from the README to update the generated index.html file with your changes:

// If you don't have redoc-cli, install it
$ npm i -g redoc-cli serve

$ redoc-cli build swagger.yaml -o index.html
$ serve -s .

@EleekaN
Copy link

EleekaN commented Nov 2, 2022

Hi @navinpai, I have done some baseline work for 'auth' endpoints. Need some inputs and feedback before I proceed further . I will create a pull request, please have a look.

@Peaaboo-Madton
Copy link

Hello, do you still need help with the documentation? I see the last update was 28 days ago.

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 good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants