-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allowing empty response body #672
Conversation
@raymondfeng Could you please confirm if the proposed fix looks okay? |
@braj1999, could you please add test(s) for your changes? |
@dhmlau Added unit test to the PR, please have a look. |
@braj1999, there's a test failure which is likely caused by your change. Could you please take a look? https://github.com/loopbackio/strong-soap/actions/runs/7456242838/job/20427083943?pr=672
|
@braj1999, with the latest code in your branch, the tests failed for Node.js 20 and higher:
This corresponds to this test case: https://github.com/loopbackio/strong-soap/blob/master/test/wsdl-test.js#L81-L86. Since the error changes to an AggregateError after Node.js 18, we could possible have the assert statement from:
to:
I've tested the above snippet. It works for both Node.js 18 and 20. |
About the commit linter error, if you could squad your commits and have a commit message something along the line as below, that should get rid of the error.
|
@dhmlau Fixed the UT |
For loopbackio#671 Signed-off-by: braj1999 <[email protected]>
@braj1999, thank you for fixing the test cases as well. I've also resolved the last failing test in your PR. |
Description
Allowing empty response body case
Related issues
For #671
Checklist
guide