search

opengeospatial / bblocks-postprocess

0 stars 0 forks source link

Handle remote YAML or JSON schema missing #16

Closed rob-metalinkage closed 8 months ago

rob-metalinkage commented 9 months ago

When a reference to a remote schema is only available as YAML or JSON the processing fails:

e.g.

Error resolving reference https://raw.githubusercontent.com/opengeospatial/ogcapi-records/master/core/openapi/schemas/recordGeoJSON.json from /workspace/build-local/annotated/geo/geodcat/dcat-records/schema.json

it is to be expected that normative references are only available as one of JSON/YAML in many cases..

avillar commented 9 months ago

This happens because of a blanket yaml -> json replacement in the schemas when generating the annotated JSON version. Need to update the code so that only references to known BB schemas are replaced. I've pushed a fixed that I think should fix this.

Where is this repo (i.e., can I test this)?

rob-metalinkage commented 9 months ago

Geodcat-api-records

avillar commented 9 months ago

Is this working now? I see that the workflow for geodcat-ogcapi-records is running without errors now.

avillar commented 8 months ago

I'm closing this as it seems to be fixed, please reopen if that's not the case.