Pradeep Kumar AV

I can add more info on this issue: In version 1.1.1 of this package we used to get the attributes returned by the vCenter and that is missing in v2...

I was able to work around the issue by doing the below steps to the returned importSpec: ``` delete response.importSpec.instantiationOst response.importSpec.instantiationOst.id = '' delete response.importSpec.instantiationOst.section; delete response.importSpec.instantiationOst.child[0].section; delete response.importSpec.instantiationOst.child[0].child; response.importSpec['@xsi:type']...

@bhoriuchi About the attributes: in v1 @nagavenkatab code returns the importSpecParams with xsi:type attribute, however no such attribute is returned in v2

One top of the head logical flaw I saw was the extendedType closest match was comparing the intersection length with the parentType to begin with, which is kinda wrong. Thats...

@bhoriuchi would you mind If we push some pull requests to fix any bugs we see ?

@bhoriuchi Thanks ! In the mean time I am trying to see if v1 solves @nagavenkatab 's code

@bhoriuchi I agree 100 percent. v1.1.1 is simpler to debug and faster to develop because its in a single project

I just used v1 to generate @nagavenkatab's ImportSpec and used it in V2 after some xsi label massaging and the import works perfectly !!! May be we need to revisit...

the master seems to have this issue now: ``` ReferenceError: babelHelpers is not defined at new SoapConnectClient (C:\testvc\node_modules\vsphere-connect\index.js:1627:9) ```