Skip to content
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

Fixed some issues with xsd elements #1057

Merged
merged 3 commits into from Apr 12, 2019
Merged

Conversation

zanemcca
Copy link
Contributor

  • Namespace was not fetched properly when definitions.xmlns[type.prefix] is undefined. There appears to be a small typo in the logic that was fixed. Please comment if this logic was intentional and we can discuss it.
  • Some types are still strings when the defaultsDeep is called. Explicitly checking for strings before calling defaultsDeep resolves the issue

@coveralls
Copy link

coveralls commented Apr 11, 2019

Coverage Status

Coverage remained the same at 93.284% when pulling 9a757c8 on zanemcca:fixed-xsd-errors into 33e170e on vpulim:master.

@jsdevel
Copy link
Collaborator

jsdevel commented Apr 11, 2019

please fix the build

@zanemcca
Copy link
Contributor Author

I updated the first patch to be more specific to the particular use case. I am a node-soap newb so any input on the fix would be appreciated.

@jsdevel
Copy link
Collaborator

jsdevel commented Apr 12, 2019

can you add a test?

@zanemcca
Copy link
Contributor Author

Test added :)

@jsdevel jsdevel merged commit 630d80d into vpulim:master Apr 12, 2019
@jsdevel
Copy link
Collaborator

jsdevel commented Apr 12, 2019

thanks!

@zanemcca
Copy link
Contributor Author

Thank you @jsdevel! When should I expect this to be published?

@jsdevel
Copy link
Collaborator

jsdevel commented Apr 12, 2019

we're due for a publish soon. i may have time in the next few days

lfantone pushed a commit to flybondi/node-soap that referenced this pull request May 20, 2019
* Fixed some issues with xsd elements (vpulim#1057)

* Fixed some issues with xsd elements

* Made the fix more specific to the particular usecase

* Added a test for aliased namespaces

* Release v0.27.0

* Move @types/request to dependencies (vpulim#1059)

soap's d.ts files depend on request. Unfortunately, since request
doesn't ship its own types, that means consumers of soap also need
@types/request. Currently @types/request is just a dev dependency, which
doesn't get installed by `npm install`. The fix is to move
`@types/request` to the dependencies list.

The error looks like this:

```
node_modules/soap/lib/client.d.ts(4,26): error TS7016: Could not find a declaration file for module 'request'. '../../../tests/cases/user/soap/node_modules/request/index.js' implicitly has an 'any' type.
```

Note that this only shows up when consumers compile with --strict, which is
fairly common.  Typescript's user-code tests include soap and detected
it after 0.27 shipped.

* Release v0.27.1

* Updated read me to reflect changes in soap.listen (vpulim#1060)

* Updated Read.me to reflect changes in soap.listen

* Updated Readme.md

* Updated Readme.md

* Updated Readme.md

* types: move forceSoap12Headers to IWsdlBaseOptions (vpulim#1063)

"forceSoap12Headers" works on server since bcc41e6. So, this option
should be available to server as well.

* client.addSoapHeader() dynamic SOAP header (vpulim#1062)

* Added support for parsing of doubles and floats. (vpulim#1065)

* Added support for parsing of doubles and floats.
package-lock updated due to out-of-date version.

* Reverting changed package-lock file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants