You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like some numeric precision gets lost when using opts_read_json(promote_num_to_string=TRUE). This only appears to happen when a multi-type row is read in, triggering the numbers to convert to character so the object imports as a character matrix.
For some added context, we're using yyjsonr in our package here for that's reading in data from a specific schema. Our package is here.
The standard calls for the data frame writing out as rows, which can have mixed types. On read, we promote numbers to strings because the data reads in as a character matrix which can easily be converted to a data frame, which we then handle all type conversions using the appropriate metadata.
It looks like some numeric precision gets lost when using
opts_read_json(promote_num_to_string=TRUE)
. This only appears to happen when a multi-type row is read in, triggering the numbers to convert to character so the object imports as a character matrix.Here's a reprex:
Created on 2025-01-28 with reprex v2.1.1
The text was updated successfully, but these errors were encountered: