Closed gitowiec closed 6 years ago
Interesting error. I'm able to replicate this error with the same WSDL and the cause of the weird output seem to be from the soap
library. I haven't investigated enough to be exactly sure why it gives that result for this specific file.
The type information is extracted using soap::Client.describe()
for v0.x, perhaps you should try using it directly and then open an issue over at the soap library if you see that the error persists.
Sorry for not being able to help out more at this time.
I just did
and got this strange thing:
That interface is wrong, it is not compatible with TypeScript, in case I am doing it wrong, how to use wsdl-to-ts?
Here is whole generated file https://gist.github.com/gitowiec/4e279a83a0fe404e46f5937474fbfc88