Correct coordinate parsing logic for lat & long for several locales #254
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Although #189 addressed the #188 issue of editing latitude and longitude fields in collections, some users are still experiencing an exception when modifying these fields:
This PR proposes a different approach to fully resolve this issue by ensuring latitude and longitude values are consistently converted to valid double formats, independent of user locale. This aims to prevent data truncation errors by enforcing a standard format across all inputs.