Question: How to provide something to a single or multiple screens?

[TheManuz]

I've took some time to experiment with this package.

It's surely interesting, but I think the package is still young and I've found a little hard to achieve some things.

Example: I want to wrap a group of screens with a Provider (a BlocProvider to be precise, but it could've been a RepositoryProvider, a Listenable, anything that I want to be visibile from the context).

For this, I have to group the routes into a sealed class group, so I can provide a KaiselShell of this sealed subclass, just to be able to use the chromeBuilder.

But now I've spawned another navigator, since I have a KaiselShell with a single shell, and the default back buttons from the Scaffolds are broken.

Maybe I'm trying to apply the wrong pattern here, I don't know, but providing things with context is a basic thing to do in Flutter.

[Hackmodford]

I don't think this is something you can really do with the Navigator in Flutter.

My understanding is the Navigator creates a stack for the child pages. Which means if you have pages A,B,C, C is not a child of B, and B is not a child of A. This is why packages like riverpod or provider have you put the provider at the root level of the app.

[TheManuz]

I understand.

To avoid having it a the root level of the app (which was the reason I faced this problem in the first place), the only solution would be to spawn a new navigator which have those providers at its root.