Onboarding step navigation and Android back
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
Research direction
Read lib/screens/onboarding_screen.dart and the setup guide at docs/getting-started/first-contribution.md; wait until issues #9, #10, and #11 have merged before starting. Implement the flow in lib/onboarding/onboarding_flow.dart and cover it in test/onboarding_flow_test.dart, checking retained values, system back, step indicators, submit outcomes, and the privacy link. Done means the listed acceptance checks pass with flutter test and flutter analyze.
Written by the indexing model from the issue text.
Description
What to build
Host the three steps (#9 name and year, #10 major, #11 courses) in OnboardingScreen: a step indicator, Next/Back between steps, state kept when moving back, and the Android system back button moving to the previous step (on step 1 it leaves the app as usual, not to the sign-in screen). On the last step's submit, call a OnboardingSubmitter interface (Future<void> submit(name, year, major, courses)) that a later issue implements against Supabase; for now the app wires a stub that completes immediately and calls AuthController.retry(). Keep the existing privacy link visible on step 1.
Files
lib/screens/onboarding_screen.dart- new
lib/onboarding/onboarding_flow.dart(state holder) - new
test/onboarding_flow_test.dart
Acceptance
- Values entered on a step survive Back then Next.
- System back (
tester.pageBack()or aPopScopetest) goes to the previous step; on step 1 it pops normally. - The step indicator shows 1 of 3, 2 of 3, 3 of 3.
- A failing submitter shows an error and stays on step 3; a succeeding one calls
retry(). - The privacy link test in the existing suite still passes.
How to check
flutter test; on the emulator walk through all three steps and press Android back.
Before you start
Setup is in first contribution. Run flutter analyze and flutter test before you open the PR; both must pass. Keep the change to the files listed. Comment on this issue to claim it.
Blocked by
- #9
- #10
- #11
Do not start until these have merged; the Blocked-by relation on this issue lists them too.
- Dominant language
- PLpgSQL
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from DevDogsUGA/DogPack
-
discover
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
DevDogsUGA/DogPack#14 ·
-
onboarding
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
DevDogsUGA/DogPack#10 ·
-
good first issue onboarding
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
DevDogsUGA/DogPack#8 ·
-
good first issue onboarding
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
DevDogsUGA/DogPack#7 ·
-
good first issue polish
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
DevDogsUGA/DogPack#4 ·
All issues in DevDogsUGA/DogPack
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
software-mansion/argent#1427 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OneBusAway/onebusaway-ios#1518 ·
Maintainers usually reply within 2 days
-
priority:p0
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeixio/toskar-core#546 ·
Maintainers usually reply within 1 day
-
direct-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aaronified/fluenough#500 ·
Maintainers usually reply within 1 day
-
VerificationCodeInputField: iPad Return key clears/hides OTP fieldsPossibly taken @amansingh1207 claimed this today. Openneeds attention
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
firebase/FirebaseUI-iOS#1407 ·
Maintainers usually reply within 5 days