-
Notifications
You must be signed in to change notification settings - Fork 4
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
Expose api functions for accessing swagmap data #10
Comments
This sounds reasonable to me, though I think there's a dependency on us settling on a schema for swagifacts (and I think a further dependency on that is figuring out a standard notation for skills so that swagifacts can say what they provide/require in a consistent way) |
...I have some thoughts on this ^^^^, and will try to expand them into a proposal while I work on preparing my conference stuff. |
Awesome! Although it doesn't require that we settle on the schema finally, we can still evolve it... But, yeah, we do need something to start with... So a suggestion would be an array of objects with the following keys:
|
Good point about building in the assumption of an evolving spec. Relevant to that: tunapanda/swagmaps#6 |
If we're going to stick with using github for the moment, we can just use the github api to get a list of swagmaps, we would need to store them all in the top level for convenience though. something like Then use rawgit.com to retrive the actual json, |
Suggestion:
.../api/swagmaps
Returns an array where each element contains information about a swagmap, minimum data would be id, name and description.
.../api/swagmap/
Returns an array of swagifacts for the swagmap with specified id.
The text was updated successfully, but these errors were encountered: