Suggest to remove singleton OpenAPI object and make Clients instanced.

Currently the Client templates reference a single OpenAPI reference which is used to set the token or headers.

An example where this approach fails is trying to contact two API’s with the same generated codegen, we frequently do this e.g. from staging to live environment stagingapi.product.com -> api.product.com and there isn’t really a workaround other than set the token before every request.

This does lead on to the question as to why the client functions are templated as statics, I believe having to instance the clients and provide the configuration would work better with DI and testing frameworks.

[cmcnicholas]

We’ve ended up forking (great project as a base btw) as we wanted some additional’s like:

• interfaces for services
• instance based services (not static)
• exposing of the request options as functions
• remove global singleton OpenApi
• add discriminator to unioned namespace
• ability to override catchErrrors
• inject an ErrorFactory
• ability to override parsing of the body

I think that’s it https://github.com/yottaltd/openapi-typescript-codegen/tree/feature/yotta-codegen

keep in mind this is only on the fetch templates currently, we have no need for xhr but will be updating the node templates accordingly.

[mb21]

For us, the --name option was not flexible enough, so we let the user pass in a whole template for the services: https://github.com/ferdikoomen/openapi-typescript-codegen/pull/1268