Vasily Martynov
Vasily Martynov
Removed requests and replaced uuid with built-in crypto.randomUUID(). Also run a smoke test against latest node 14, all worked, so we still support node 14+.
I've just published new release 1.0.4 with some improvements. Planning to include this PR in the next release and increment minor version (1.1.0) as it contains some pretty major changes....
Hi @JbIPS, Okay, happy to discuss proposed solution.
I had another look on it ... that is not that easy, deepmerge-ts is not enough. Some stuff can be replaced with native JS features, but not all. Too much...
Did you mean X.509? Is this a feature request or a bug report? That is that implementation? Is there some server that does not expect ``?
Sorry, this is still not clear to me. Is this a bug report or a feature request?
I don't think I understand the problem, sorry. Could you provide WSDL, code snippets, what are you expecting and what result are you actually getting.
yeah, I think this one should be closed and new one created if problem is still there.
Looks like WSDL file is not correct. But there is not enough information. Could you provide WSDL files and code snippets how do you run the server and/or client.
@smokhov, I rebased that PR, but some existing tests failed.