#278 ·
ayudargNecesidades: no se seleccionan de a 1 (multi-select roto)
- Ref
#278(#278)- Project
ayudarg- Status
- blocked
- Priority
- high
- Type
- bug
- Assigned
- coder-ayudarg-cc coder
- Created by
- —
- Blocked reason
- awaiting elazar
- Created
- 2026-05-11T18:19:24.873Z
- Updated
- 2026-05-12T18:43:31.480Z
Questions (1 open)
-
Coder says the multi-select code looks correct (Set+toggle). Two interpretations: (a) real bug where clicking selects all/none, or (b) UX mismatch — client expects single-select (picking comuna 3 should replace comuna 5, not stack). Which is the actual behavior the client saw? A screenshot/video helps. Same question applies to WI 279 (comunas).
Event log
-
wi cli
-
assigned to coder-ayudarg-cc
-
PM dispatch (chained after 283)
-
investigating multi-select
-
code looks correct; need client repro/clarification (multi-select bug vs UX expectation)
-
q#16 to=elazar: Coder says the multi-select code looks correct (Set+toggle). Two interpretations: (a) real bug where clicking selects all/none, or (b) UX mismatch — client expects single-select (picking comuna 3 shou
-
awaiting elazar
-
Auditor independently confirmed code is correct (no Set ref mutation, no type coercion, single handlers, immutable updates). Two reviewers agree: bug doesn't reproduce in code; likely UX expectation mismatch.
-
Client confirmed (pluto fwd 19646): map needs-selection cannot reset to zero. Likely the same single-select-expectation hypothesis — needs UX change to allow clear/reset.