Single source of truth for geo coordinate formatting
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by comparing the client-side geo-coordinate formatting with the formatting returned by xforms-engine, including the manual padding and space removal described in the issue. Investigate how the engine's codec functions and client formatting can stay synchronized without assuming the codec must be exposed. Done means establishing a sustainable single source of truth that prevents formatting regressions and reactivity loops.
Written by the indexing model from the issue text.
Description
Description
We implemented a manual format for geo coordinates on the client side (padding integers with .0 and removing spaces). This was required to ensure the client's emitted value matches what xforms-engine returns, preventing a reactivity loop that was destroying in-flight map edits. Having formatting in both places isn't ideal, since it can easily regress.
Investigate the best architectural approach to establish a single source of truth for geo coordinate formatting.
- Exposing the engine's internal codec functions was considered during the fix, but this doesn't cleanly fit the engine's current structure.
- The solution doesn't strictly have to be sharing the codec, as long as we can find a sustainable way to keep the client and engine formatting in sync.
- 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