Current Behavior
Meshery's REST API endpoints are defined in server.go, but not well-commented or externally documented.
Desired Behavior
Using Swagger, Meshery's REST API documentation should be auto-generated and published. Ideally, published to the Meshery documentation site (https://github.com/layer5io/meshery/blob/master/docs), if feasible.
Resources
@nupur-thakur Any updates over here ?
@kushthedude I wanted to learn about swagger when i assigned this task to myself and I searched a bit but got stuck and then I forgot about this issue, sorry for that.
But if recently when @leecalcote mentioned it in #780 It got my attention so I will start working on it again.
If you already know about swagger and have some time could you please help me with this?
@nupur-thakur I thing swaggo will be better for us, as it is a lot simpler and lighter than go-swagger. Also, @leecalcote Where are we planning to host the API documentation. Do we need auto-deploy with every commit ?
Also, will we need dredd after setting up API documentation?
@leecalcote If this hasn't been resolved yet, I'll like to work on this. I have looked into using Swagger and as @kushthedude said, swaggo will be a better option to use here.
Green light here. Yes, Swaggo supports both net/http and Gorilla, which is great.
Is there space for a newbie to jump in for learning purposes and a portfolio item please?
Hi @Documentus sure there鈥檚 more than enough space馃憦馃徑, I hope it鈥檚 not too late? I welcome you to join the Layer5 community here - http://slack.layer5.io to collaborate with other contributors.