Sailor push not work as I expect with CupertinoTabScaffold innter TabViews.

[kishansinhparmarxongo]

How I push with sailor and without sailor.

Routes.sailor.navigate(
                          "Inner1",
                          navigationType: NavigationType.push,
            );

Navigator.of(context).push(
                        MaterialPageRoute(
                        builder: (context) => Inner1(),
                     ),
           );

My Flutter layout inspector.

Observe (with sailor)
3 bottom tabs
[Inner Tab Screen stack]
(https://github.com/kishansinhparmarxongo/resources_link/blob/master/Inner%20screen.png)

Expect (Without sailor)
3 bottom tabs
Inner Tab Screen

You can follow this link UX expect

[kishansinhparmarxongo]

Something in context I tested today. If I create my own "onGenerateRoute" even it not works.
So problem somewhere around context.

[amrnt]

The way to fix this maybe to enable another optional routing with the context.

[kishansinhparmarxongo]

Actualy I skipped sailor for my next upcomming projects let just grow sailor more stable. Thanks

[amrnt]

I understand. I'm trying to make some experiments around this.

In theory, the best way is would be routing using the closest GlobalKey<NavigatorState> in the tree. I tried to work around this with inherited widget etc but that was too much.

Let's see what @gurleensethi would say about this

[kishansinhparmarxongo]

@amrnt Great to discuss with you.

Yes, With the same I also try to make my own navigation service with GlobalKey but its an experiement stage so I have not wider practise around it.

Hope something that @gurleensethi will find about it. I realy love sailor package.