Add --bail cli flag, exit with non-zero status if scanning results in error, fixes: #370 #371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature request #370
When using the
swagger-jsdoc
cli in an npm scriptIf the scan fails the process currently exits with an exit code
0
which indicates successWhen running on CICD for example,
I would like the job to fail so the process would need to exit with non-zero code
This PR adds a cli flag (
--bail
), when the flag is set exit with non-zero code if scanning failse.g.
If the scan fails, the script exits with code
1
otherwise it exits with0
as normal