-
Notifications
You must be signed in to change notification settings - Fork 648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XlsxReader casting integers cells to blanks #882
Comments
So, I made some changes to the XlsxReader to change the behavior as I needed ( I also made some changes so it's easier to use the code base in our project): I made two changes:
I added a basic test for this behavior: I would be willing to make a PR for these changes on this repo. I was not sure if the maintainers are interested in these changes, so let me know. |
Column type detection uses all column cells to determine the columnType instead of only the first one.
Column type detection uses all column cells to determine the columnType instead of only the first one.
@Afollet If you have time to check and can test with the current master version I think that this issue must be solved |
@lujop Can I pull down the snapshot of this version of master? I think that would be easiest for me to test it, but I'm was not able to pull it on https://oss.sonatype.org/ Could you advise me on how to use maven to test these changes? |
@Afollet you can just clone the repo and do a |
Hello devs,
Thanks for making/maintaining this library. I am currently in a microservice that validates the data in excel spreadsheets.
I'm reading an excel workbook with multiple sheets in tablesaw-excel.
I have cell types in Excel of both numeric and text in a column. When the table is read in, the numeric cell types become blank cells. Therefore, when I try to pull up missing values I get the rows where the numeric type cells are at
Is there some way I can change the behavior of this using XlsxReadOptions? Or is there another method I can use to avoid this behavior?
Thanks!
The text was updated successfully, but these errors were encountered: