More than one generated Client Api will result in an Extension Method Conflict for ConfigureRefitClients

[robpalm]

Is your feature request related to a problem? Please describe.
If you have more than one generated Client Api which use DependyInjectionSettings, then the generated ServiceCollection Extensions ConfigureRefitClients will Conflict.

Describe the solution you'd like
Add a new Setting, e.g. ExtensionMethodName, in DependyInjectionSettings with Default Value: ConfigureRefitClients

[christianhelle]

@robpalm Thanks for taking the time to report this

I haven't thought about that scenario. I built that feature for myself and my teams and our use case was the API's we build come with a client SDK (nuget package) so that consumers of our API's only have to install the nuget package. This works very well for me and my teams, at least for the backend side of things

Anyway, your request is trivial to build so I'll see if I can implement it tonight

[christianhelle]

@robpalm I think you should be able to work around this by specifying different namespaces for different clients

[christianhelle]

@robpalm You're more than welcome to build the feature yourself. Just create a PR and if all tests are green then let's get it in and publish a release

[christianhelle]

@all-contributors please add @robpalm for ideas

[allcontributors]

@christianhelle

I've put up a pull request to add @robpalm! 🎉

[robpalm]

@robpalm I think you should be able to work around this by specifying different namespaces for different clients

I think that is possible only if you split up the DI Setup in different classes, one per client, with different namespace using.

I can build it and create a PR. Thanks!