[Feature] Offer Modal Service as a cascading value rather than requiring injection

I’ve been wondering recently whether the modal service being injected is the right thing to do. Looking at the designs from the Blazor team, they favour using cascading values to provide global concerns. AuthenticationState being a good example of this.

The proposal is to provide a CascadingModalService component which can be added at the app level rather than requiring the developer to inject a modal service. Ideally, this would also replace the need for adding the BlazoredModal component to the MainLayout.

I’m interested in others thoughts on this. Do you have any scenarios where an injected service is a necessity over a cascading value? Love to get some feedback on this idea.

[chrissainty]

Yes @larsk2009 that’s it. It just seems like it would solve several reoccurring setup issues we keep seeing, as you’ve pointed out. Without much of a down side. Unless I’ve missed something 🙂

[MichelJansson]

@chrissainty Thanks for the lightning fast reply. Ok, interesting none the less.

For me personally, who started using asp.net core last year because Blazor came around, it feels more intuitive to inject external things, and I would not expect to access a external service thru a cascading parameter. One more thing for the toolbox when designing services - thanks!