-
Notifications
You must be signed in to change notification settings - Fork 76
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
Improve detectDates. closes #288 #291
Conversation
9b1011b
to
45d7fdc
Compare
Codecov Report
@@ Coverage Diff @@
## master #291 +/- ##
==========================================
+ Coverage 67.70% 67.71% +0.01%
==========================================
Files 34 34
Lines 8897 8900 +3
==========================================
+ Hits 6024 6027 +3
Misses 2873 2873
Continue to review full report at Codecov.
|
3730ae8
to
5b5340f
Compare
I still have issue, with a file that was simply written by openxlsx and then read back again (so Excel has never been near it). write.xlsx(CVAD_list, "CVAD list.xlsx") Error message from the third line above is as follows: Error reading date: There's nothing obviously odd about cell F59. I'm happy to create an example that I can post if it would be useful. packageVersion("openxlsx") |
Hi @cha-petersumm , you can have a look at |
Thanks. That does appear to load from CRAN now, and it does fix the problem with dates. Great work! As per https://cran.r-project.org/web/packages/openxlsx2/index.html. |
Hackish attempt to fix #288
This PR checks if there is a numeric value, at a position, where we already expect a string of this type "yyyy-mm-dd". For whatever kind of reason, we end up here, with a numeric value in #288. Most likely due to the date being a POSIXct. Therefore most likely the fix is at the wrong position and should be somewhere else. For this minimal test file it should not matter, though with larger files we might waste a lot of time testing the conversion.