Conversation
|
Is there any intrinsic reason that the group element is commented out and parsed as |
|
Could you please add some tests for this? it would help to understand the changes and lock down the implementation. Thanks. |
IMO, it's history the OG devs would know. Whatever was the reason, we don't need to dwell on it, and push the project forward, so thank you for your contribution. I see in your fork you also did commit an implementation of the sequence ordering; that other branch has tests. Do they cover this group element as well? if so, then why not include it into the PR as well? It seems from your implementation |
|
|
||
| public $ref?: string; | ||
|
|
||
| // XSD allows min(/max)Occurs, but node-soap currently only pluralizes on element level |
There was a problem hiding this comment.
Could you also explain this comment in relationship to:
node-soap/src/wsdl/elements.ts
Line 207 in 012457e
I am curious.
|
If you can't add a test for this change, I can do this, but I need example WSDL and ideally expected request response. Thanks. |
They have a some test WSDL and a test for the squence ordering in their other branch, maybe can use that? |
|
Ah, I will have a look a bit later, thanks for checking this. |
Working on a change that allows respecting the order imposed by
xs:sequencein schema, which is an existing issue (#1267).Respecting the
xs:groupelement is also of importance since there are specific cases when the sequence appears as a child of the group.