-
Notifications
You must be signed in to change notification settings - Fork 47
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
STAC API spec validity? #8
Comments
I'm currently working on spectral validation for the OpenAPI file, but the API spec repo is pretty new so thinks are just starting and the CI is not even activated yet... Regarding the OpenAPI link issue... I agree that linking JSON Schema is not allowed as $ref, but I don't see which relation this has with the quoted definition for "pattern"?! |
@bdelliott Which tool would you use? It seems that Spectral doesn't check external references... |
@m-mohr Sorry, I pasted the wrong snippet. Should make more sense now. I was able to get validation working using swagger-cli (https://www.npmjs.com/package/swagger-cli) Will post a PR when I get a few mins. |
Thanks! Let's see how #10 works out and then we may add swagger-cli in addition. :-) |
Sounds good - my laptop just died so happy to let that one back for a bit |
There are actually even more invalid things in the OpenAPI file :-( |
Discussed in sprint, goal is to
To get a basic version working, then we wait for #31 |
@matthewhanson - can you take this one soon? Hoping for beta.1 release soon. |
…d} to replace geojson with stac items #8
The STAC API OpenAPI definition references an external JSON schema document for the GeoJSON definitions, which is disallowed by the OpenAPI v3 spec:
From section 4.7.24.1 (http://spec.openapis.org/oas/v3.0.3#properties)
The problem lines are:
I will submit a PR to add validation to the CircleCI to enforce spec validation unless someone is already doing this.
The text was updated successfully, but these errors were encountered: