Generated types clash and fail to compile about wsdl-tsclient HOT 5 OPEN

If fixed this using a JS script that patches the files after having generated the code. It's more of a workaround than a real fix of the wsdl-tsclient library.

I can share the script if you want to. I used regular expressions to find and replace the duplicates.

const lServiceExportRegEx = /export { ([A-Za-z]*) } from ".\/services\/\1";/gm;
const lPortExportRegEx = /export { ([A-Za-z]*) } from ".\/ports\/\1";/gm;
const lPortImportRegEx = /import { ([A-Za-z]*) } from "..\/ports\/\1";/gm;
const lServiceInterfaceRegEx = /readonly ([A-Za-z]*): \1;/gm;

const lServiceSubValue = `export { $1 as $1Service } from "./services/$1";`;
const lPortSubValue = `export { $1 as $1Port } from "./ports/$1";`;
const lPortImportSubValue = `import { $1 as $1Port } from "../ports/$1";`;
const lServiceInterfaceSubValue = `readonly $1: $1Port;`;

from wsdl-tsclient.

Any news on this or #46 ? Have any maintainers went through this ?

from wsdl-tsclient.

I have a similar situation where the wsdl-tsclient CLI made duplicates :

Any idea how I could fix this ?

from wsdl-tsclient.

I ended up just manually adding aliases for the clashing names, like:

export { WebPaymentApi as WebPaymentApiService } from "./services/WebPaymentApi";
export { WebPaymentApi as WebPaymentApiPort } from "./ports/WebPaymentApi";

Same in the services/WebPaymentApi.ts file (alias for port).

I don't mind that much as I only have one service and my wsdl is quite stable. But would be nice if the the tool would detect those kind of duplications itself - or at least provide a standardized way to provide aliases. It seems like it's not very unlikely that a real-life wsdl would result in duplications like that...

If it would bother me more and/or I had the time, I might try to fix it myself with a pull request...

from wsdl-tsclient.

Still an issue for us.

from wsdl-tsclient.