Add documentation for the state of the library with depency injection.

[antonioortizpola]

After playing a little with the new library, I noticed that some classes seem to be ready to be used with dependency injection, while others not.

I can see there is a ServiceCollectionExtensions for authentication for example, that also calls services.AddForgeService(configuration) to add the SDK base.

But then, it does not add AuthenticationClient, same with AddForgeService, which does not add the SdkManager, but adds the ForgeService, which is not used then on the ApsClient initialization,

This makes the use of dependency injection more difficult, since we need to override the forge service after initialization.

This also makes me question about how the initialization is shown on the examples, because it is creating a new service collection to get the HttpClient, Instead of letting the web application to handle the HttpClient creation.

Would not be better to use dependency injection as default and this just as a workaround? Is there a plan to add a Tutorial or demo integrated with .Net hosted service or web app?

About that, is there a plan to fully integrate the library with DI? I know I can get it to work with DI, for example (more work needs to be done, just an example)

But, if there is a plan on your side to integrate and document this integration, I would prefer to wait to use the same code and standard.

[sajith-subramanian]

Thanks for the suggestion. While we do not have a plan to address this as of now,,I can log this for further investigation.