hi, its me again, working behind a corporate proxy isn't the best...
As you can see down in strip-definition | line 263 it's trying to asssign an empty object to responses.
Since the description dosen't have a response the code breaks.
Not sure why it has to be an empty response, can't it just be deleted?
This behavior is problematic if the removeResponses flag is set.
And a description is provided on the path (see #50)
The response gets changed bevor all descriptions get stripped, that's why #50 didn't fix the real issue...
Furthermore I added a few more tests, to actually test the combination of all options in the presets.
I used a paramerized test to check if a api spec gets stripped properly. The array contains the preset and the expected stripped spec.
BTW: you got two high findings, that can be easly fixed by upgrading wait-on to 7.2.0 😅
Description
hi, its me again, working behind a corporate proxy isn't the best...
As you can see down in
strip-definition | line 263
it's trying to asssign an empty object toresponses
. Since thedescription
dosen't have a response the code breaks. Not sure why it has to be an empty response, can't it just be deleted?This behavior is problematic if the
removeResponses
flag is set. And adescription
is provided on the path (see #50) The response gets changed bevor all descriptions get stripped, that's why #50 didn't fix the real issue...Furthermore I added a few more tests, to actually test the combination of all options in the presets. I used a paramerized test to check if a api spec gets stripped properly. The array contains the preset and the expected stripped spec.
BTW: you got two high findings, that can be easly fixed by upgrading
wait-on
to 7.2.0 😅