We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have this :
AutoRoute( page: FeatureIndex.page, path: 'feature-index', children: [ AutoRoute( page: FeatureStep1.page, path: 'feature-step1', initial: true, ), AutoRoute( page: FeatureStep2.page, path: 'feature-step2', ), ], )
I navigate to FeatureIndex, routing automatically to FeatureStep1 because it's initial route. Then, I navigate to FeatureStep2 from FeatureStep1.
FeatureIndex
FeatureStep1
FeatureStep2
On FeatureStep2, which is a StatefulWidget, I call setState to set a value.
StatefulWidget
setState
From FeatureStep2, I navigate to FeatureIndex, routing automatically again on FeatureStep1 because it's initial route.
When I call context.router.removeWhere on FeatureStep2 to remove FeatureStep1 before navigate to FeatureIndex, there is these strange side effects :
context.router.removeWhere
dispose
All these side effects don't exist when removeWhere is not called.
removeWhere
You can find a demo repo just here : https://github.com/fabienbranchel/auto_route_remove_where_dispose
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I have this :
I navigate to
FeatureIndex
, routing automatically toFeatureStep1
because it's initial route. Then, I navigate toFeatureStep2
fromFeatureStep1
.On
FeatureStep2
, which is aStatefulWidget
, I callsetState
to set a value.From
FeatureStep2
, I navigate toFeatureIndex
, routing automatically again onFeatureStep1
because it's initial route.When I call
context.router.removeWhere
onFeatureStep2
to removeFeatureStep1
before navigate toFeatureIndex
, there is these strange side effects :dispose
ofFeatureStep2
is not calledFeatureStep2
is not removed from stackFeatureStep2
fromFeatureStep1
, the state is not resetAll these side effects don't exist when
removeWhere
is not called.You can find a demo repo just here :
https://github.com/fabienbranchel/auto_route_remove_where_dispose
The text was updated successfully, but these errors were encountered: