Mix this.configuration and _options instead of _config || this.configuration can make api easier for use.
For example I have a system which manage lots of apps, and I set userKey in the createConfiguration to manage apps. When I want to send notifications to one app, I can set the apiKey in the _options parameter, but I also need to provide parameters like baseServer, httpApi and middleware. Mix this.configuration and _options can make properties of the _options parameter optional.
Create a new DefaultApi instance every time is a way to solve this problem, but sometimes I want to make sure that only one instance exists, like using with NestJS.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What's on your mind?
Mix
this.configuration
and_options
instead of_config || this.configuration
can make api easier for use.For example I have a system which manage lots of apps, and I set
userKey
in thecreateConfiguration
to manage apps. When I want to send notifications to one app, I can set theapiKey
in the_options
parameter, but I also need to provide parameters likebaseServer
,httpApi
andmiddleware
. Mixthis.configuration
and_options
can make properties of the_options
parameter optional.Create a new
DefaultApi
instance every time is a way to solve this problem, but sometimes I want to make sure that only one instance exists, like using with NestJS.Code of Conduct