FilledStacks / FilledStacks/flutter-tutorials
Provider Tutorial example isn't responsive as it's shown on the tutorial (010 and 012) itself
- Vorherrschende Sprache
- Dart
- Sterne
- 4.8k
- Forks
- 1.7k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Hi Dane,
These days I'm experimenting with Flutter and trying to find out an easily maintainable, straightforward, and readable architecture.
So I stumbled upon the architecture you are teaching for Provider (yes there are many successors now such as StackedProvider and RiverPod, but I want to learn from the beginning).
I followed two of your videos:
- Flutter Provider Architecture for State Management | Flutter Provider
- Written: https://www.filledstacks.com/post/flutter-architecture-my-provider-implementation-guide/
- Flutter Provider - A Follow up to my Architecture Guide
- Written: https://www.filledstacks.com/post/flutter-provider-architecture-sharing-data-across-your-models/
Most of the application works fine as shown on the video tutorial. But it doesn't appear to be that much reactive/responsive as it's shown on your Videos. Two main issues are:
- After login, the posts fetching API call doesn't get called properly, needs to try for the second time.
- Like counts don't get refreshed properly as shown on the tutorial.
Herewith I have attached my source code as well.[ (Google Drive link to download the source code and the screencast)](https://drive.google.com/drive/folders/1CuyFvRbggrMDNeZV3-tqkI8pVQP8ov_w?usp=sharing)
I experimented and tried so many things to figure out what's wrong with it.

Could you please let me know what you think of the error in it?
P.S.:
I even downloaded the source code from your GitHub repository and tried it out still it too has the same issue.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Das Issue verweist auf die Provider-Tutorialbeispiele 010 und 012 und verlinkt die entsprechenden Artikel; beginne damit, die Abläufe für Login, das Abrufen von Posts und das Aktualisieren der Like-Anzahl mit dem Quellcode des Repositorys nachzustellen. Als erledigt gilt es, wenn der erste Login Posts abruft und die Like-Anzahlen ohne einen zweiten Versuch aktualisiert werden.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- dart, flutter
- Bereich
- mobile-dev
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100