those I can probably just match up manually
I found schemas like https://api.apis.guru/v2/specs/azure.com/automation-softwareUpdateConfiguration/2017-05-15-preview/swagger.json that contains reference to definition in relative document "$ref":"./definitions.json#/definitions/softwareUpdateConfigurationCollectionItem” but I cannot find definitions.json near the schema file https://github.com/APIs-guru/openapi-directory/tree/master/APIs/azure.com/automation-softwareUpdateConfiguration/2017-05-15-preview
I there any way to resolve such references? // cc @IvanGoncharov
We've launched an Open Collective fundraiser to help cover the hosting costs of the openapi-directory. If you find the directory useful, or integrate with it, please consider donating. Thank you. https://opencollective.com/openapi-directory
Just a heads up that we're now looking at adding our first OAS 3.0.x definitions to the directory. To distinguish them, the filenames will be openapi.yaml/openapi.json but everything else should be the same. At the moment there is no plan to downconvert these definitions to OAS 2.0 - please let me know if either of these considerations are likely to be a problem for you.
FYI, yesterday I gave a talk to dive into this topic as part of an interview process. I'm quite intrigued by this problem space and can see some interesting tasks to work on: https://steveej.github.io/slides/zhaw-techtalk-0/#36 feel free to take a look from the beginning and start discussing with me, pointing me to things, or both
I don't know of anything specific, but you could use something like https://github.com/ColinEberhardt/json-transforms to massage the input JSON, then, if needed, one of the OAS libraries (see openapi.tools) to create the final OpenAPI definition. If you find something, it would be useful to share it, so it can be used for APIs-guru/openapi-directory#188
FYI: the source format in question is https://github.com/joelvh/cloudcheckr/blob/master/lib/cloud_checkr/api/endpoints.yml
cloudcheckr.com provides an endpoint that exposes the known endpoints in JSON format. the linked file is a cache of it in YAML form
unfortunately it lacks result information
Other languages are (I believe) available. :smile: There are some good JSON transform tools available in Java I think. If you can find a nice DSL to OpenAPI tool you like, it looks like piping the YAML through that would be quite easy. There's only really the parameter information there, and you're going to have to default quite a lot of the OpenAPI boilerplate.
You might have more luck using the HTML API reference here http://support.cloudcheckr.com/cloudcheckr-api-userguide/cloudcheckr-api-reference-guide/ and using https://github.com/bobby-brennan/scrape-to-swagger if you're happy with regexes and CSS selectors.
the firefox web console doesn't seem to support things like :contains, but I'd like to fully comprehend the examples
@MikeRalphson it seems that the openapi-codegen has not attracted much attention during the last few months. I'm about to spend some time on this topic again and am wondering which project to contribute to. I've found https://github.com/OpenAPITools/openapi-generator which has gained some momentum
As I said to someone else recently, it comes down to whether you prefer a dsl driven or code driven approach, and nodejs vs java, and how much community support you want. Between swagger-codegen and openapi-generator I think it's too early to tell, but the main difference is between the larger breaking changes in sc and more continuity with og.
in particular I'm interested in generating Go and Rust server and client code which supports http and apiKey security schemes
Completeness can only really be measured by working configs /languages, but it should quickly tend towards 100%
it allows for replacing the parser implementation
if one wanted that
looks like it's called authData in the code (https://github.com/Mermade/openapi-codegen/blob/b2d93b4d95932bd6fd370caee46f5b1973010983/adaptor.js#L175)
is this range missing the for indentation? https://github.com/Mermade/openapi-codegen/blob/master/adaptor.js#L66-L115
I have no new experience in javascript since looking at this project a couple months ago :D
I found https://github.com/wework/speccy which is very helpful at finding errors and it also providers some useful lint rules