Add information for error handling into swagger node template #91
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.
Proposed changes
When the node generated from swagger encounters an error (ex. HTTP 404), it throws the error and a catch node can catch the error in the current implementation. But the error event does not contain the details of the error. Therefore, it is difficult for the flow after catch node to handle the error. To solve this problem, I added information (same as http request node) for error handling into swagger node template.
Checklist
gruntto verify the unit tests pass