Splitting one yaml into different files and setting validateSpec=false still results in parser failure

[SteveGueldner]

Hi!

When I split an openapi.yaml like this...

openapi.yaml
... paths: /stuff: $ref: "./stuff/methods.yaml"

methods.yaml
get: tags: - stuff operationId: getStuff responses: "200": description: OK content: application/json: schema: type: string

...and set validateSpec=false compilation still says that methods.yaml is invalid because "Unrecognized token 'get'".

Additionally this is logged, which is not logged when omitting validateSpec=false:
Cannot invoke "io.swagger.v3.oas.models.OpenAPI.getExtensions()" because "openAPI" is null

Versions used:

quarkus-openapi-generator: 2.6.0-lts
Quarkus: 3.15.2
Java: 21
maven-compiler-plugin: 3.9.6

[ricardozanini]

Server or Client?

[SteveGueldner]

Client :-)

[ricardozanini]

The subfiles are not being added to the processing IIRC, that's why it's ignoring the ValidateSpec attribute.

[SteveGueldner]

This would be a really useful feature. For large API definitions splitting files totally makes sense. But I don't want to end up having 100 files in a root directory.

[SteveGueldner]

I just checked how the generator behaves if I put everything in the root directory. It still throws the same exception. Of course I changed the path to the underlying yaml accordingly and set validateSpec=false.

[ricardozanini]

@SteveGueldner feel free to submit a PR. I can help review it.