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
is there a way to skip processing cells based on their excel defined format(e.g. Number)? we have users who upload excel files that are displayed one way in excel, but get converted to floats when they are processed through calamine.
this screenshot shows the issue. the csv was generated by saving the xlsx file as a csv. the last two columns have the Number format applied and get converted to floats before getting converted back into strings.
ideally, those values would get preserved as strings to avoid things like differences in float precision adding a bunch of extra digits or truncating trailing or leading 0s. is there a way to do that currently? i made a small repo showing the problem using the deserialize function to specify that the output should always be String
oh hmm. i didn't realize that excel would export the CSV based on what was displayed rather than what the actual value was. i guess i shouldn't be surprised excel does something unexpected. thanks for looking at this.
is there a way to skip processing cells based on their excel defined format(e.g.
Number
)? we have users who upload excel files that are displayed one way in excel, but get converted to floats when they are processed through calamine.this screenshot shows the issue. the csv was generated by saving the xlsx file as a csv. the last two columns have the
Number
format applied and get converted to floats before getting converted back into strings.ideally, those values would get preserved as strings to avoid things like differences in float precision adding a bunch of extra digits or truncating trailing or leading 0s. is there a way to do that currently? i made a small repo showing the problem using the
deserialize
function to specify that the output should always be Stringhttps://github.com/TomPridham/calamine-float
The text was updated successfully, but these errors were encountered: