Return types are not unique across services. They conflict.

[ianberdin]

Return types are not unique across services. They conflict.

[ianberdin]

If we don't specify an operationId, the API will look like this:

api.users.usersControllerCreate() -> UsersControllerCreateResponse
api.carts.cartsControllerCreate() -> CartsControllerCreateResponse
api.bookings.bookingsControllerCreate() -> BookingsControllerCreateResponse

[mrlubos]

Try https://heyapi.vercel.app/openapi-ts/migrating.html#v0-46-0

[ianberdin]

Wow, it works as expected!
Thank you.

[mrlubos]

Hey @ianberdin, is this a regression?

[ianberdin]

No, it's not. I can't use the next version 0.46.* because it breaks completely, so I'm using 0.45.3.

[ianberdin]

There is no this on root file, I see it does not use classes anymore (0.46.*):

[ianberdin]

Thank you for your quick response. The issue with this has been resolved.

The main problem now is non-unique names when using a custom operationId. Is there a way to fix this?

[ianberdin]

And this, if I set new hey-api fetch client:

[mrlubos]

Not that I'm aware, will need to look at this. Thanks for reporting!

[ianberdin]

If I remove the operationId, it will look like this:

api.users.usersControllerCreate() - not very appealing for a customer-facing API :(

[mrlubos]

Are you on Discord @ianberdin? Would like to understand your use case better

[ianberdin]

I've sent you a request in Discord.
@ianberdin mine username.

[mrlubos]

I think you can resolve this with services.methodNameBuilder(), let me know if not