The select1 with "map" appearance shows "Point saved" when no itemset options loaded
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Reproduce the issue with the “Select one from map bounds” form and its bounds.geojson attachment, then trace the select1 map appearance and status banner behavior when the GeoJSON features have empty properties. Done means an empty option list no longer produces “Point saved” without a selection, and the behavior is covered by an appropriate test or verified against the reproduction.
Written by the indexing model from the issue text.
Description
Expected Behavior
When the GeoJSON itemset data is malformed (missing the id / title properties used by the form), the form should not claim that a selection has been made. Either no "Point saved" should appear, or the form should surface a clear "options could not be loaded" error so the form author can fix the data.
Observed Behavior
The map renders with no pins, but the status bar reads "Point saved" as if the user had selected something. Nothing is actually selected, the consumer's option lookup matches undefined === undefined against the empty option list, so the UI treats the empty current value as a valid selection.
Reproduction Steps
Form (XML or XLSX file): Select one from map bounds.xml + attachment bounds.geojson (features have empty properties: {}).
https://test.getodk.cloud/projects/649/forms/Select%20one%20from%20map%20bounds/submissions
Steps:
- Open the form for a new submission.
- Navigate to the select1 appearance="map" question.
- Without tapping any pin, observe the map and the status banner.
Environment
- Browser version:
- OS:
- Web Forms version:
- Dominant language
- TypeScript
- Stars
- 38
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 getodk/web-forms
-
iOS
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 Half a day Newbie friendliness 54/100
-
Offline send queueOpenIn Enketo
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Launch form offlineOpenneeds discussion
Difficulty 5/5 Over a week Newbie friendliness 38/100
All issues in getodk/web-forms
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
twilio/twilio-node#1241 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hugomrdias/playwright-test#786 · 1 comment ·
Maintainers usually reply within 1 day
-
area:stdlib effort:S impact:med platform:linux type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
WenyuChiou/agent-board#1745 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day