Go: openAPI "epsg-code" issue

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

Go: openAPI "epsg-code" issue #23

Closed bgoesswe closed 5 years ago

bgoesswe commented 5 years ago

@m-mohr: I tested the DefineStringFormat function with the newest kin-openapi3 version and it works fine now, but in the coreAPI there is still one format type "epsg-code" that causes issues. I can not redefine it, because it is not of type "string", but "number". There is currently no possibility to define non-string formats in kin-openapi3. Should we change the type in the API to string? We can also keep it and I create an exception for it.

m-mohr commented 5 years ago

Well, an EPSG code is a number and it is inherited from STAC so we can't change it. It would produce invalid responses. Also, I don't think it is correct to change the API due to a tool that is not well implemented. kin would need a DefineNumberFormat or at least let users define custom formats that are ignored. I'd suggest opening an issue with them.

bgoesswe commented 5 years ago

Ok I created an issue and added the exception for now.