Node.js and field names as input to ipgm.js and xmlservice about xmlservice HOT 4 CLOSED

Original comment by Magne Kofoed (Bitbucket: magnekofoed, GitHub: magnekofoed).

Ok, thanks, I've moved this issue to nodejs-itoolkit.

from xmlservice.

Original comment by Aaron Bartell (Bitbucket: aaronbartell, GitHub: aaronbartell).

A: Maybe. However any change to an existing interface may affect current node scripts.

Should be able to add it to the "options" portion of the call without disrupting existing API signatures. But as Tony declares, this needs to be documented as an issue on the nodejs-itoolkit repo.

from xmlservice.

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

This is NOT an XMLSERVICE issue (already works as you suggest). Please move your issue to the offending node toolkit (this is your problem).

https://bitbucket.org/litmis/nodejs-itoolkit

from xmlservice.

Original comment by Tony Cairns (Bitbucket: rangercairns, GitHub: rangercairns).

Unhelpful part ... xmlservice is not the problem ... 'names' are not a restriction in XMLSERVICE. That is, any added 'attribute' to xml comes back out ...

#!xml
<pgm name='ZZCALL'>
 <parm><data type='1A' var='myname' feild='myname'>a</data></parm>
 <parm>
  <ds var='myds' feild='myds'>
:

Helpful part ... the real issue is this particular node toolkit, which has an abbreviated idea of conversion from XML to JSON.

So, real question should be ...

Q: Can we change the 'interface' of the node Toolkit to allow additional 'user attributes' that return in json.

A: Maybe. However any change to an existing interface may affect current node scripts.

from xmlservice.