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.
Description
We implemented a manual format for geo coordinates on the client side (padding integers with
.0and 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.