Added generic add functions

[WhiteOlivierus]

Pull Request Template

Description

I took some inspiration from how the Microsoft DI container registration works and added those functions to Reflex. The options I added are:

• Generic Add functions (these will give you warnings in your IDE if you cannot register something)
• Generic Add functions that will return a specific construction of the registered type

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] AddSingleton_ValuableWithIValuableAsContract_ShouldNotThrow
• [x] AddTransient_ValuableWithIValuableAsContract_ShouldNotThrow
• [x] AddSingleton_SpecificValuableWithIValuableAsContract_ShouldNotThrow
• [x] AddTransient_SpecificValuableWithIValuableAsContract_ShouldNotThrow
• [x] AddInstance_SpecificValuableWithIValuableAsContract_ShouldNotThrow

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] I have checked my code and corrected any misspellings
• [x] I have checked that Reflex.GettingStarted still runs nicely

[gustavopsantos]

Awesome to see you started the implementation for adding function support, however I think its better to create a specific new API like AddSingleton,AddTransient. Something like AddFunction. To add this new functionality without poluting the current APIs. Also when adding function support, we need to add debug support, so the debugger window should be able to display the correct informations. So in min mind the following steps needs to be followed. 1 - Update debugger window to display the objects created under each binding (VContainer has something pretty similar) 2 - Add new AddFunction API 3 - Test both the AddFunction API and also resolving it

[WhiteOlivierus]

Hey thank you for the quick reply.

I extended the current api, and this is still backwards compatible like this. Because the idea is too have specific constructions for all of the lifetimes that you can register. If we would make a addfunction method we should give it a lifetime when creating it, while we could just make a specific function like I did now.

[gustavopsantos]

Overloading current APIs and extending current resolvers will affect both, current behaviour and performance. Basically we want to provide a functionality where user can detach the object creation from container controlling it by himself while keeping created objects disposal within parent container. I will provide a new API AddFunction or AddFactory that will allow this without changing current behaviour and perf for existing Resolvers (Transient, Singleton and Instance)

[WhiteOlivierus]

I'm so sorry, I was swamped lately, but here I have an example of what I mean why I want this way of registering services. Now I get an error when running the container that something is wrong. But with the generic functions, it would never let me register this which would not be resolvable.