felangel / felangel/flow_builder

When the AppFlowData changes, every page in the stack is rebuilt (can I get around it?)

Aperta
#47 2 commenti 3 reazioni 1 assegnatario Rivendicata da @felangel Vedi su GitHub
bug
Lingua principale
Dart
Stelle
416
Fork
68
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

**Describe the bug**
This is probably more of a question than an actual bug. Every change I make to the AppFlowData causes every page that is in the stack to rebuild itself. The problem is that I need for a particular page (the homepage) to show some animations and perform an API call when it first loads, however, when the home page adds another page to the stack or the page added is popped, for example, the homepage is rebuilt, showing the animation again and calling the API once more.
This is not the same behavior as if you are using named routes in the MaterialApp. I want to know if this is the expected behavior and how (if possible) I can get around it.

**To Reproduce**
Steps to reproduce the behavior:
1. Create two pages and a FlowBuilder that starts only with one of them
2. On a button click on the first page, change the FlowData to add the other page to the stack
3. When you click the button (or pop the second page for that matter) you will realize that the first page was rebuilt.

*I made an example in [**this repository**](https://github.com/LucaDillenburg/Flutter-Navigation-Example).*

**Expected behavior**
I believe the expected behavior should be the same as if you were using Flutter's regular routes system (MaterialRoute with routes property): when a page is added or removed from the stack, the other pages are not rebuilt.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.