brianegan / brianegan/new_flutter_template
What kind of Routing should be supported?
- Dominant language
- Dart
- Stars
- 138
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Assuming we work with a list view / detail view application, what kind of routing should the template employ? Should it worry about Flutter Web urls? Should it have some url parsing to demonstrate the concept? Should it use simple Navigator.push? What is important for routing in a template?
Please note: we've been asked to hold off on Navigator 2.0 for now.
- onGenerateRoute that supporters `/entity/{id}`
- onGenerateRoute placeholder that only goes to HomePage / DetailPage
- Navigator.push
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the routing options listed in the issue: onGenerateRoute for `/entity/{id}`, a placeholder onGenerateRoute, and Navigator.push. Check the existing template structure and its HomePage and DetailPage entry points, while respecting the note to hold off on Navigator 2.0. Done means the template has a documented, agreed routing approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100