Mastersam07 / Mastersam07/deepa
Disparity between router api and navigator api example
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Observation
The router API adopts nested navigation, while the navigator API sample adopts flat navigation.
This can be noticed in the behaviour of both examples.
Effect
For the navigator API sample, deep-linked screens are pushed to the top of the stack even when they are meant to be the child of nested navigation.
Proposed solution
Migrate navigator API sample to nested navigation
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the router API and navigator API examples, focusing on how each models nested navigation and handles deep-linked screens. Migrate the navigator API sample to nested navigation, then verify that deep-linked screens appear as children of the intended navigation rather than at the top of the stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100