Please ignore "anyOf type null"

[ways]

Describe the bug

I generate my openapi spec using pydantic. When there are optional values, pydantic will output such:

"anyOf": [
                {
                  "$ref": "#/components/schemas/ValuesAxis_float_"
                },
                {
                  "$ref": "#/components/schemas/CompactAxis"
                },
                {
                  "type": "null"
                }

The validator does not like this null value, and gives:

Value 'null' does not match required pattern 'boolean|object|array|number|integer|string'

I'm not sure who are correct here, but I think it might be pydantic.

To Reproduce
Steps to reproduce the behavior:

1. Create a model in pydantic with an optional field.

class Axes(CovJsonBaseModel):
    x: Optional[Union[ValuesAxis[float], CompactAxis]] = None

2. Look at resulting openapi spec.

Expected behavior

Allow "type: null" if the field is not required.

Additional context

Example openapi.json: https://github.com/metno/edrisobaric/blob/main/docs/openapi.json

[dstenger]

Thank you for reporting.
We will do further investigation.

[ways]

Seems null is allowed in openapi 3.1, but not in openapi 3.0.

Reference: https://redocly.com/docs/openapi-visual-reference/null/

[ghobona]

@ways The Executable Test Suite only supports OGC API - Environmental Data Retrieval (EDR) version 1.0.0 and 1.0.1.

These versions of OGC API - EDR only support OpenAPI 3.0.

If you would like future versions of OGC API - EDR to support OpenAPI 3.1, please create a GitHub Issue at https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/issues

[ways]

If you would like future versions of OGC API - EDR to support OpenAPI 3.1, please create a GitHub Issue at https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/issues

Seems that's already discussed here opengeospatial/ogcapi-environmental-data-retrieval#375

I will leave my service as it is, and ignore the validation problem for now.