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
{{ message }}
This repository has been archived by the owner on May 26, 2022. It is now read-only.
Following on from #481, I still think there is a need for returning raw cell data.
The attached xlsx has a cell C2 with a custom format which is is incorrectly recognised as a date.
The cell has a value 1 formatted to look like 1 ST, spout returns this as: { "date": "1900-01-01 00:00:00", "timezone_type": 3, "timezone": "UTC" },
Presumably becuase it thinks it's getting a date starting with: 1st ....?
If I use $reader->setShouldFormatDates(true); then spout returns: #,##0 ST
Neither is correct. If I had the option to return raw cell data I could at least extract a value of 1 and work with that.
@melihyenel You should not need such an option if the library returns you the right data :)
@devops-at-alinea What do you expect Spout to return? If the cell has a timestamp value set to 1, it's normal that it returns { "date": "1900-01-01 00:00:00", "timezone_type": 3, "timezone": "UTC" }.
When setting $reader->setShouldFormatDates(true);, you expect Spout to return "1 ST" right?
Spout does not seem to be able to interpret the #,##0 part... I need to look into this
Following on from #481, I still think there is a need for returning raw cell data.
The attached xlsx has a cell C2 with a custom format which is is incorrectly recognised as a date.
The cell has a value
1
formatted to look like1 ST
, spout returns this as:{ "date": "1900-01-01 00:00:00", "timezone_type": 3, "timezone": "UTC" },
Presumably becuase it thinks it's getting a date starting with:
1st ....
?If I use
$reader->setShouldFormatDates(true);
then spout returns:#,##0 ST
Neither is correct. If I had the option to return raw cell data I could at least extract a value of
1
and work with that.test.xlsx
using "box/spout": "^2.7",
The text was updated successfully, but these errors were encountered: