fix(openapi): return rejected Promise
if spec uploads fail
#409
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.
🧰 Changes
Turns out we had an edge case where we were returning a
console.log()
rather than a rejectedPromise
when we received errors from the API, resulting in an incorrectly successful exit code. This PR fixes that in 0f2372e so we properly return an exit code of 1. And as expected, some housekeeping:Promise
rather than a console output 8811c8cPromise
error outputs to be padded with newlines 9936de5Resolves #407.
🧬 QA & Testing
If the tests pass, we should be good! But as an extra check, you can check out this branch and run the following commands to confirm that we see a non-zero exit code: