Open kdomingo opened 1 year ago
Same issue
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 ^^;
There was also this comment that could be useful
@kdomingo could this isseu be closed ?
Navigating to an item's details screen and going back makes the list screen rebuild.