brianegan / brianegan/flutter_architecture_samples

Redux add/edit screen doesn't use store

Open
#153 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Dart
Stars
8.9k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

I was wondering the reasoning behind the `AddEditScreen` not using the store to save its state. I would've liked to see how redux is supposed to be used in the scope of editable textboxes. Should I have an action for each edit of the textbox?
How do I decide whether I should use the global state or just use a `StatefulWidget`?
Why was a GlobalKey used here?
How does the Navigator work with Redux? For instance, should I use the Navigator to route different pages of a shared bottom navigation, or just use a property of global state like in the provided example?

Contributor guide

Open the contributing guide

Research direction

Start with the AddEditScreen and the provided Redux example, then trace the StatefulWidget, GlobalKey, editable textboxes, and Navigator usage mentioned in the issue. Done means the project provides clear guidance on local versus global state, textbox actions, GlobalKey usage, and navigation with Redux.

Written by the indexing model from the issue text.

Assessment

Tech stack
dart, flutter, redux
Domain
mobile
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.