-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verbose CLI output to help troubleshoot (especially in composed mode) #495
Comments
@reuvenharrison , any hint on how to understand what file/element is triggering this error? |
Hey This kind of issue can appear in schemas that use an |
@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. |
Hi @anikitin,
What do you think? |
@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. |
Trying to troubleshoot an issue when running oasdiff in composed mode (I use oasdiff 1.10.9)
It really lacks the option to show what file (and endpoint/operation) it is currently processing.
I.e. I am trying to generate a changelog from a tree with hundreds of openapi files in composed mode (with
--flatten-allof
).And I am getting just this in output:
At this point I just need something like
--verbose
to get more information about where it stopped.Then I will try to figure out what is wrong top report a different issue (maybe)
The text was updated successfully, but these errors were encountered: