Verbose CLI output to help troubleshoot (especially in composed mode) about oasdiff

[anikitin]

@reuvenharrison , any hint on how to understand what file/element is triggering this error?

[tcdsv]

Hey
This error occurs when trying to merge schemas that have entirely separate enum value sets. Because there are no shared enum values, there is no data that could be considered valid against both of the schemas.

This kind of issue can appear in schemas that use an allOf component and have more than one enum field.

[anikitin]

@tcdsv , thanks. I would be happy to dig deeper into this problem, but I need to understand what particular file and schema triggered it (out of 200+ I included into scan)...

Actually all our specs are validated and linted, so there should be no incompatibilities in terms of OpenAPI standard.

[reuvenharrison]

Hi @anikitin,
As a first step to resolve this I suggest adding the problematic file name to the error message, like this:

Error: failed to load base specs from glob "../api-metadata-specs2/openapi/*/*-openapi.yml" with failed to load "path-to-problematic-file" with unable to resolve Enum conflict: intersection of values must be non-empty

What do you think?

[anikitin]

@reuvenharrison , yes, for sure. But since files can be pretty big we need also to refer somehow to problematic schema/component within this file as well.