Closed LasneF closed 5 months ago
oh dear, this error comes from here: https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v3.1/schema.json, its not something I can control, this rule is parsing the schema and validating it. I think the schema needs updating to allow it.
Looking deeper into this: Here is when the schema validator pulls out when validating against the latest 3.1 schema:
It's pointing here: https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v3.1/schema.yaml#L211
good raising the topic to the OAS community
this will be addressed when this will be merged / fixed https://github.com/OAI/OpenAPI-Specification/pull/3355
The latest OpenAPI 3.1 schema has been added into libopenapi
and absorbed by vacuum
in v0.8.7
and this issue is now resolved.
given the pattern below
paths: /orders: $ref: paths/orders.yaml
it looks not supported as giving me the below error \openapi.yaml:33:11 | error | schema invalid: not allowed | oas3-schema | Schemas | $.paths['/orders'].$ref .\openapi.yaml:35:11 | error | schema invalid: not allowed | oas3-schema | Schemas | $.paths['/orders/{order-id}'].$ref
BUT this pattern is valid according to OAS https://spec.openapis.org/oas/latest.html#fixed-fields-6
it should be managed as any $ref