This PR introduces the contents of passing an error to callback when an ErrorResponse from KAS comes as a response.
Previously, ErrorResponse was also processed as data, but in this case, it is more difficult to handle errors, so change to throw as an error in case of ErrorRseponse.
Types of changes
Please put an x in the boxes related to your change.
[ ] Bugfix
[ ] New feature or enhancement
[x] Others
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules
Related issues
Please leave the issue numbers or links related to this PR here.
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Proposed changes
This PR introduces the contents of passing an error to callback when an ErrorResponse from KAS comes as a response.
Previously, ErrorResponse was also processed as data, but in this case, it is more difficult to handle errors, so change to throw as an error in case of ErrorRseponse.
Types of changes
Please put an x in the boxes related to your change.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Related issues
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...