-
Notifications
You must be signed in to change notification settings - Fork 40
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
Audit fails with $ref that points to another file and contains ~1 #54
Comments
Could you provide sample of your OpenAPI file? |
Where would you like me to send it? I can not post it online. |
Could you post it to [email protected] ? I tried to reproduce the issue using the paths with ~1s but it worked for me. Perhaps the problem is more specific to your OAS, so it would be very helpful to have it. |
Sent as requested |
Thanks for sharing the sample! I see the issue occurring now. I'll let you know once I have ETA for a fix. |
I have fixed issue in the VS Code extension, which was causing "Unable to locate node" errors. However, unfortunately for your OAS file the audit functionality is still unusable. The issue is that in a few places you're referring to some individual properties of your 'Custom' schema, for example: This is something for us to fix, but for now audit functionality effectively can't be used with your API. |
Yes, i have since refactored my openapi files to remove those. It was unnecessary. Thank you, i am now able to perform security audit. |
I am getting the error
Trying to audit my file.
The path element in question is:
Which is a valid reference.
The text was updated successfully, but these errors were encountered: