Issue with docs/handbook/dependency-inversion/index.md

[dimacurotech]

It is absolutely unclear how to register/start using Splat within Xamarin.Forms. Simply registering interfaces+implementations within Splat's Locator.CurrentMutable does not make Splat a default DI container.

[glennawatson]

Splat is everywhere throughout reactiveui code base. So we make calls to splat to determine which views or adapters are used. You have no choice in some capacity to use Splat but we are starting to add DI adapters to allow it to talk to other engines

[dimacurotech]

I guess this talk does not give a clear reference to an article, so here it is: https://reactiveui.net/docs/handbook/dependency-inversion/

Dependency Inversion

ReactiveUI is a composable, cross-platform model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming which is a paradigm that allows you to express the idea around a feature in one readable place, abstract mutable state away from your user interfaces and improve improve the testability of your application.

[glennawatson]

Thanks for the feedback something we can make more explicit for sure

[dimacurotech]

@glennawatson What I ment was that it is completely unclear how to integrate Splat into a new Xamarin.Forms project.
Such a project uses Xamarin.Forms.DependencyService as a default service locator.
So the key question here is: how to make Splat a default Service locator?

The article shows how to register services and how to manually resolve them. But will ReactiveUI resolve them automatically after that? Or should we take another step?

Maybe we do not need that another step and can use Splat side by side with Xamarin.Forms.DependencyService?

[glennawatson]

You can definitely work side by side with it. We are adding a bunch of DI engine adapters to Splat at the moment so might add to the list the Xamarin.Forms.DependencyService as an adapter.

What this does is makes Splat's backing store for the values whatever DI engine is used in the adapter.

[dimacurotech]

Do you plan to add IServiceCollection (for registration) and IServiceProvider (to resolve) from Microsoft.Extensions.DependencyInjection?

[RLittlesII]

I am wondering what the desire is to have a web DI Adapter for a UI framework that targets desktop and mobile? Not saying that we shouldn't or won't do it, I am just trying to understand the sell. Is WPF going to be wiring into the same abstractions? The framework currently sits under asp.net which is not a framework we support at the moment.

[glennawatson]

Some people use it in web frameworks (eg Geoffrey Huntley has used it in this case).

[dimacurotech]

Sorry for late reply - I've been busy with another project.
@RLittlesII, it is really strange why Microsoft.Extensions.DependencyInjection.Abstractions sits under asp.net, but it provides a great standard for different libraries, since many libraries already provide extensions for IServiceCollection.

I wouldn't drop Microsoft.Extensions.DependencyInjection.Abstractions just because it sits under asp.net, not under something else.

On the other hand: if it does not suit ReactiveUI because of technical reasons - than of course it should not be supported.