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 issue when an error was undefined: undefined #771

Merged
merged 1 commit into from
Nov 2, 2015

Conversation

tomgco
Copy link
Contributor

@tomgco tomgco commented Nov 2, 2015

This occurs on responses that from what I can tell do not have an
xsi:type of string, Thus these objects would not have an internal $value
and would return undefined.

This commit keeps backwards compatibility and falls back to assuming the
error was a string.

This occurs on responses that from what I can tell do not have an
xsi:type of string, Thus these objects would not have an internal $value
and would return undefined.

This commit keeps backwards compatibility and falls back to assuming the
error was a string.
@herom
Copy link
Contributor

herom commented Nov 2, 2015

Looks good to merge 👍 - thanks a lot 😄

herom added a commit that referenced this pull request Nov 2, 2015
Fixed issue when an error was undefined: undefined
@herom herom merged commit 6b5702b into vpulim:master Nov 2, 2015
@SEAPUNK SEAPUNK mentioned this pull request Nov 3, 2015
@jguepin
Copy link

jguepin commented Dec 4, 2015

Do you plan to release a new version on npm with the fix soon? Thanks!

@bnetter
Copy link

bnetter commented Dec 15, 2015

👍

1 similar comment
@Manuel-Manoury
Copy link

👍

@jsdevel
Copy link
Collaborator

jsdevel commented Dec 15, 2015

done @jguepin sorry for the delay.

diarmaidm pushed a commit to diarmaidm/node-soap that referenced this pull request Feb 3, 2016
Fixed issue when an error was undefined: undefined
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
6 participants