The purpose of the go_router for Flutter is to use declarative routes to reduce complexity, regardless of the platform you're targeting (mobile, web, desktop), handling deep linking from Android, iOS and the web while still allowing an easy-to-use developer experience.
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.
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
.