Go: Enable usage of unmodified openEO specification

Open-EO / openeo-backend-validator

Service to validate back-end compliance with the API specification.

Apache License 2.0

1 stars 3 forks source link

Closed bgoesswe closed 5 years ago

bgoesswe commented 5 years ago

Add the possibility to use the unmodified OpenAPI specification of openEO These things have to be figured out to make it possible:

add custom type for "url" (currently replaced by "url") see https://github.com/getkin/kin-openapi/issues/79
epsg-code had to be removed to make it work(may be same issue as before)
server had to be removed to make it work --> find a way to ignore it
security makes problems if there is only an empty version --> is maybe already fixed but needs to be tested.

m-mohr commented 5 years ago

Let me know if there's anything I can help with.

m-mohr commented 5 years ago

bgoesswe commented 5 years ago

Yes, but couldn't make it work by now, but I am still on it

m-mohr commented 5 years ago

There was also a problem with nullable, which is due to the OpenAPI spec being not very clear about its behavior. I fixed this in the openEO API spec itself, see commit https://github.com/Open-EO/openeo-api/commit/64bfc62bdb0cf94a5fa1f63756ab50e242f5d136#diff-81a4213b3282d6ebe982e56a204421ca

bgoesswe commented 5 years ago

With this commit I ruled out these validation steps of the openAPI file validation:

After that I was able to use the unchanged coreAPI JSON and also use the openapi.json directly from github.