-
Notifications
You must be signed in to change notification settings - Fork 234
Fix security vulnerabilities #425
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
base: master
Are you sure you want to change the base?
Conversation
- Migrate from `swagger-parser` to successor `@apidevtools/swagger-parser` - Bump dev packages with security vulnerabilities - Fix cleanup issue with test when files do not exist
|
Thank you for this PR. I would like to see this PR merged. However, it appears that this project is no longer active. |
|
@martin-badin could you please merge this PR in our project we are blocked and it's impacting our production also |
|
Sorry. I am not owner. |
|
@daniloab Do you be able to review and merge this PR? |
Hey, I'm going to review. Sorry for the late. |
| tryUnlink(`${dir}/swagger.json`); | ||
| tryUnlink(`${dir}/customSpec.json`); | ||
| tryUnlink(`${dir}/customSpec.yaml`); | ||
| tryUnlink(`${dir}/customSpec.yml`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can also just skip removing this non existent file (instead of wrapping in try/catch)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this failing or the try catch is working as expected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try catch is working as expected. But the .yml file doesn't exist - so we can alternatively just remove line 152 (like I do in my other PR).
swagger-parserto successor@apidevtools/swagger-parser