You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 25, 2022. It is now read-only.
Hello, I am refactoring my apps to use this amazing router (thanks for this wonderful work ^_^). However, I noticed that when context.go/context.goNamed is called, the caller widget is rebuilt before navigates to the other page. I don't know if this behavior is expected or not, but using Navigator.push/Navigator.pushNamed does not happen this.
When you navigate from Home page to the Second Page, then "rebuild Page home" is printed showing that the Home Page is rebuilt while calling context.goNamed.
The text was updated successfully, but these errors were encountered:
Hello, I am refactoring my apps to use this amazing router (thanks for this wonderful work ^_^). However, I noticed that when
context.go
/context.goNamed
is called, the caller widget is rebuilt before navigates to the other page. I don't know if this behavior is expected or not, but usingNavigator.push
/Navigator.pushNamed
does not happen this.I am using this code:
When you navigate from Home page to the Second Page, then "rebuild Page home" is printed showing that the Home Page is rebuilt while calling
context.goNamed
.The text was updated successfully, but these errors were encountered: