Closed cvarona closed 1 year ago
I've never tried such a setup. Can you share an example project that reproduces the issue?
Sure!
Ooops. When preparing the bundle for uploading I realized it was a wrong import that was causing the issue. I had neglected to export the api configuration class in the public api, so the class was being directly fetched from the source folder rather than from the output folder (dist). When done ok it works perfectly, both with and without a module.
Sorry for the false alarm!
Regards
Hi,
it's being impossible for me to programatically modify the generated client's root url in my application.
Environment:
Despite the generated client's configuration class's injection being marked as 'provided in root' I will get a different, newly created instance in my app component, which will render any attempt to modify the root url for all generated and imported services meaningless.
Even if a generate a module (
RestClientModule
) and configure it upon bootstrapping:importProvidersFrom(RestClientModule.forRoot({rootUrl: environment.aDifferentRootUrl}))
the problem will still be the same.Any idea about how to circumvent this other than setting the url in the library itself?
Regards