[Kotlin] Turn Invitación into a visitor-code form with visual validation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
Research direction
Start by reading the Invitación screen and the referenced ADR 0007, ADR 0008, and docs/api/auth.openapi.yaml to identify the visitor pass fields the API requires. Then trace the demo variant and existing unit test patterns. Done means the form validates fields while typing and on blur, enables submission only when all are valid, shows demo success or error feedback, and has validation unit tests.
Written by the indexing model from the issue text.
Description
Part of the first delivery (parent issue above, due 2026-10-23). The course asks for forms with visual validation, and today the app has none: the Invitación screen is a placeholder.
What to build
The Invitación screen becomes a form for redeeming a visitor code:
- Fields: the code, plus whatever the contract's visitor day pass needs (see ADR 0007, ADR 0008 and
docs/api/auth.openapi.yaml). Only what the API really asks for. - Material 3 validation:
isErrorandsupportingTextin Spanish (usted), with format and length checks while typing and on blur. - The submit button stays disabled until everything is valid.
- On submit in the demo variant, a success or error state from the demo data.
Done when
- Every field shows its error in Spanish when invalid, and the button enables only when all are valid.
- Unit tests for the validation rules.
- Merged into develop by 2026-10-21.
- Dominant language
- Java
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 85
Getting set up
- No Dockerfile or Docker Compose file
- No 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 K-Forge/KApp
-
area/kotlin
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
area/kotlin
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
area/kotlin
Difficulty 5/5 Over a week Newbie friendliness 35/100
K-Forge/KApp#176 · 1 comment ·
Maintainers usually reply within 1 day
-
Entrega: mockups de las 7 pantallas a partir de la app real (Alejandro)Possibly taken @Ale3320 claimed this 1 day ago. Openarea/docs
K-Forge/KApp#165 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Entrega: wireframes de las 7 pantallas (Iván)Possibly taken @Ivan-Ruiz00 claimed this 1 day ago. Openarea/docs
K-Forge/KApp#164 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
approved
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
checkstyle/checkstyle#22129 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
objectionary/lints#1577 ·
Maintainers usually reply within 2 days
-
ChaosEngine: backup-remote doctor row passes while consumer mode hides bot memory from gitPossibly taken @MohabMohie claimed this today. Openagentic
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ShaftHQ/SHAFT_ENGINE#7263 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100