Merging upstream changes #5
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* add optional targetNamespace to output message name * add test cases * add optional output for non stylised wsdl
…1177) * change content-type-parser to whatwg-mimetype * Readme.md: Rewrite how to get support for conciseness, update mentions of the old request module to Axios, improve documentation of several functions' arguments. * Reorder the import from 'whatwg-mimetype' to be alphabetized. The upstream pull request 1169 failed linting with the following error: ERROR: /home/runner/work/node-soap/node-soap/src/http.ts:9:1 - Import sources within a group must be alphabetized. * Add @types/whatwg-mimetype as a developer dependency. * HttpClient.request(): Change the call to MIMEType's constructor method to MIMEType.parse(). The MIMEType constructor method throws an Error object on failure, unlike the call to contentTypeParser() from the 'content-type-parser' package, which returned null on failure. To maintain backwards compatibility, use MIMEType.parse(), which returns null on failure. * http.ts: Change the import syntax for MIMEType to be compatible with TypeScript. * HttpClient.request(): Fix the code that gets the boundary parameter from the parsed HTTP Content-Type header. Co-authored-by: Thiago Lagden <[email protected]>
The usage of axios in this repository is very basic, but its versioning is defined very tightly. This causes problems, because the interface IOptions uses AxiosInstance as its property, preventing the clients of this library from updating their axios version beyond the limits set in this library. Typescript compiler gives type error when giving higher version AxiosInstance for IOptions. By setting axios as a peer dependency, we would allow the clients of this library to install other versions of axios if they so choose.
* added ability to add to request http header within "request", "message" events; added accompanying test which test ability to add http header within "request" event; * fixed lint error
Co-authored-by: Joe Spencer <[email protected]>
* Removed double await in async There's no need to call await again on the result object since result is already resolved. * Returning just the JSON response in await example In the example for async, logging result returns an array containing not just the JSON response but also the rawResponse, rawRequest e.t.c. This can be confusing for users who try the async example after trying the non-async examples which only return the JSON response. I added a subscript to the 0th index so that that's what's logged.
* Added override constructor to ClientSSLSecurityPFX class Added test for additional ClientSSLSecurityPFX constructor Fixed failing test of ClientSSLSecurityPFX * Disabling test using and removing files PurchasingRequestService due to 404 links
v1 is deprecated.
* feat(WSSecurity): allow using WSSecurity and WSSecurityCert together * docs: add idMode option for WSSecurityCert to Readme Co-authored-by: Florian Schmid <[email protected]>
The encrypted private key test/certs/agent2-key-with-password.pem was encrypted with DES, which is unsupported in Node.js 18. I re-encrypted it with AES, and now the build works in Node.js 18.
Use native string.trim instead of regex replace for performance. remove log line. fix quotes in tests.
Co-authored-by: John Plusjé <[email protected]> Co-authored-by: Vasily Martynov <[email protected]>
* Support binary data in MTOM Uncomment test code that was disabled when migrated from Request to Axios. --------- Co-authored-by: Vasily Martynov <[email protected]>
* Bump Axios to 1.7.4 to resolve the CVE-2024-39338 --------- Co-authored-by: Vasily Martynov <[email protected]>
- Override endpoints in some tests where it tried to send requests to the endpoints in the internet - Now tests work in offline
Co-authored-by: simakov <[email protected]>
as child element and implement attributes parsing for RestrictionElement
add tests to prove than rsa-sha1 and rsa-sha512 signature algorithms can be set
use getKeyInfoContent from xml-crypto
ensure that the regex does not backtrack excessively
* Add IWSDLCache interface which can be extended with custom caching implementations * Add DefaultWSDLCache implementation which matches current caching handling, ie global singleton which indefinitely caches WSDLs. * Add options.wsdlCache to allow users to override the default cache. * Add test cases for default cache and overriding option. * Add new option to Readme Co-authored-by: millerdk12 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.