Beamer router integration difficulties

[busslina]

You can see here:

Page keys are crucial in how Beamer manages the navigator's pages API. They identify whether pages should be updated, removed, or remain unchanged during navigation transitions. Proper use of page keys ensures that the state is preserved across navigation events and that the performance is optimized by preventing unnecessary widget rebuilds.

So I'm not being able to maintain my index screen state when navigating to another screen (push) and then going back to index (pop). I have been thinking that maybe Beamer is meant to work with StatefulWidgets and States.

So maybe flutter_rearch needs a suported routing library for this particular scenario (preserving state).

What do you think?

[busslina]

I just did a test project, comparing StatefulWidget and RearchConsumer, and I have to say I'm wrong because in both cases the state is preserved. So I must be doing something wrong in my project.

https://github.com/busslina/beamer-rearch-state-preserving-test

[busslina]

Solved. The issue was simpler than I thought. Was related to route path convention. Beamer says it is declarative, so it only maintain parent state if we stay on its path subtree. EG: Moving from / to /profile. My problem was I used /index as my root path, so moving to /profile seems to be considered to a new tree, so state is not preserved. Make sense...