Fixed
Details
Assignee
Pothys - MitrahSoftPothys - MitrahSoftReporter
Michael Born @ OrtusMichael Born @ OrtusPriority
NewNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Details
Details
Assignee
Pothys - MitrahSoft
Pothys - MitrahSoftReporter
Michael Born @ Ortus
Michael Born @ OrtusPriority
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Created 9 August 2021 at 18:28
Updated 16 June 2024 at 19:29
Resolved 2 December 2021 at 10:40
Importing a JSON document with large decimal numbers causes those decimal numbers to be converted to a string.
This makes it difficult to generate WKT polygons from JSON, for example, without manually converting the latitudes and longitudes back to a numeric value.
Here's an example:
https://trycf.com/scratch-pad/gist/29c3cceff42e80a843c33100d4193ed3