Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Onboarding step navigation and Android back

Aperta
#12 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
dart, flutter, supabase
Ambito
mobile

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

onboarding

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

Acceptance

  • Values entered on a step survive Back then Next.
  • System back (tester.pageBack() or a PopScope test) 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.

Lingua principale
PLpgSQL
Stelle
0
Fork
0
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DevDogsUGA/DogPack

Tutte le issue di DevDogsUGA/DogPack

Issue simili

Altre issue su Mobile Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.