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

investigate feasibility of swagger #76

Open
davidwallis opened this issue Jun 20, 2018 · 4 comments
Open

investigate feasibility of swagger #76

davidwallis opened this issue Jun 20, 2018 · 4 comments

Comments

@davidwallis
Copy link
Collaborator

investigate adding swagger to document the api

@davidwallis
Copy link
Collaborator Author

postman might be more practical I think :)

@Bounz
Copy link
Owner

Bounz commented Jul 9, 2018

Well, the main goal of swagger (from my point of view) is to

  1. document the API
  2. provide some kind of contract for 3rd party developers

So swagger would be suitable with HG to replace (or extend) existing documentation of Web API (like https://bounz.github.io/HomeGenie-BE/api/mig/core_api_config.html#2)

@davidwallis
Copy link
Collaborator Author

Yeah I'm just not sure that its going to work with websocketsharp and more suited to WCF / Rest style services?

@Bounz
Copy link
Owner

Bounz commented Jul 9, 2018

Well, I think it's possible, but one of the advantages of Swagger is autogeneration of swagger file and I think it's not possible in the current implementation of the backend.
So I think we should return to this question after doing some moves towards asp.net core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants