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
I noticed the same.
It seems state is only kept when the previous screen is part of the location stack.
E.g. going from LocationA -> LocationB
class LocationB extends BeamLocation<BeamState> {
@override
List<BeamPage> buildPages(BuildContext context, BeamState state) {
return [
// create whatever (back)stack you desire here.
// this will also keep the current state of this location in memory
...LocationA().buildPages(context, state),
const WidgetB(),
];
}
@override
List<Pattern> get pathPatterns => ["/b"];
}
Disclaimer: I just started using beamer 2 days ago. There could be another way I don't know yet ^^;
Navigating to an item's details screen and going back makes the list screen rebuild.
The text was updated successfully, but these errors were encountered: