[Onboarding + Enrollments] Store onboarding step values in a flow model
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What to build
Keep the student’s name, class year, major and course list while they move between setup steps. Add one shared object for those values and the current step so going back does not erase earlier work.
Files
lib/onboarding/onboarding_flow.dart(new file)- Starting example: lib/screens/onboarding_screen.dart
Code to add or extend:OnboardingFlow extends ChangeNotifier.
Steps
- Add
OnboardingFlowwith name, classYear, major, courses and step fields. Start step at 0 and the answers empty. - Add
setName(String),setClassYear(String?),setMajor(String)andsetCourses(List<String>), plusnext()andback(). Each setter stores the value and callsnotifyListeners(); store a copy of the course list. Keep step between 0 and 2. - Changing steps must keep all answers. This object stores form answers only; saving them to the server comes later.
Example
Set the name to “Ada”, call next(), then back(). step returns to 0 and name is still “Ada”.
Check it works
In test/onboarding/onboarding_flow_12_test.dart, check the example above and the failure or limit described in the steps. Run flutter test test/onboarding/onboarding_flow_12_test.dart and flutter analyze.
Before starting
- #53 — Submit valid name/year from the step
- #54 — Validate and submit the major field
- #56 — Delete a course chip and set Done state
References
Assign yourself before starting, or comment to claim the issue. Project setup.
- Lenguaje dominante
- PLpgSQL
- Estrellas
- 0
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DevDogsUGA/DogPack
-
polish
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
DevDogsUGA/DogPack#131 ·
-
polish
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
DevDogsUGA/DogPack#130 ·
-
moderation
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
DevDogsUGA/DogPack#119 ·
-
moderation
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
DevDogsUGA/DogPack#113 ·
-
discover
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
DevDogsUGA/DogPack#106 ·
Todos los issues de DevDogsUGA/DogPack
Issues similares
-
Rename Madson cameraAbierto
Dificultad 2/5 Menos de una hora Aptitud para principiantes 75/100
StoDevX/AAO-React-Native#8785 ·
Los mantenedores suelen responder en 1 día
-
Android bug feature/error-tracking react-native team/error-tracking
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
PostHog/posthog-js#5310 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
zingolabs/zingo-mobile#1656 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Happybello365/innov8#265 ·
Los mantenedores suelen responder en 3 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
callstackincubator/simlock#639 ·
Los mantenedores suelen responder en 1 día