Export for non existent path and type

Describe the bug I’ve tried to generate types and clients for the Klarna APIs. For the Checkout API and Payments API it works great, but with the Order Management API it generates an export for a type that does not match the generated type name (image). It also generates an additional export for a type in a file that doe not exist. Not sure if this is something wrong in Klarna’s OpenAPI spec (available on url above) or if this can be corrected with the code generator.

In the screenshot I have skipped generating core, services and client for simplicity. My config is:

{
	input: path,
	output: path,
	exportCore: false,
	exportServices: false,
	indent: 'tab',
	httpClient: 'axios'
}

Summary

• type address is generated and put into Address.ts
• address.ts is not generated but exported from index.ts
• type Address is not generated but exported from Address.ts in index.ts

[ajenkins-cargometrics]

Yes, can confirm I’m on Mac

In that case, a fairly easy workaround is to have the tool initially write the files to a case-sensitive filesystem, and then fix up the filenames so they’re unique ignoring case. Here’s how you could do that on a Mac.

1. Get a spare external drive, like a flash drive. Open Disk Utility, select the main partition on your external drive, select Erase, and choose the “Mac OS Extended (Case-sensitive)” format. Click Erase.
2. Now run the openapi generator, telling it to write the files to the external drive. Since it’s a case-sensitive filesystem, it should work. You’ll have separate “Address.ts” and “address.ts” files.
3. On the external drive, rename address.ts (lower-case) to something like address2.ts. Edit index.ts to change the import for “address” to import from “./models/address2”. Make a similar change to the schema file if you’re using schema files.
4. Repeat the previous step for any other files whose names differ only by case. I didn’t check if there are any others.
5. Now you can safely copy the files to your main drive.

If you have access to a Linux machine, you could also use that since they have case-sensitive filesystems by default.

[ferdikoomen]

@marjorg, @ajenkins-cargometrics is correct, the spec contains two models, only differencing in case. The best way is to have a case-sensitive file system. There is sadly no way to enforce case-sensitivity in NodeJS when writing these files 😦 @ajenkins-cargometrics thanks for the response! Much appreciated!