add escape for datatable unaware for package#5918
Conversation
|
#5655 might help with testing :-) |
|
I actually think this fix is pretty reasonable, WDYT @jangorecki? |
|
@ben-schwen I'll let you merge since this was marked as Draft but it's good to go IMO |
Generated via commit 1899eab Download link for the artifact containing the test results: ↓ atime-results.zip
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5918 +/- ##
=======================================
Coverage 98.77% 98.77%
=======================================
Files 81 81
Lines 15203 15203
=======================================
Hits 15017 15017
Misses 186 186 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
R/print.data.table.R
Outdated
| if (col.names == "none") | ||
| colnames(toprint) = rep.int("", ncol(toprint)) | ||
| if (nrow(toprint)>20L && col.names == "auto") | ||
| if (NROW(toprint)>20L && col.names == "auto") |
There was a problem hiding this comment.
Hm, could you explain these? Needing it is a bit of a code smell...
|
So, basically when deactivating p.s. I have no idea why vscode keeps adding the french |
| dim.data.table = function(x) | ||
| { | ||
| if (!cedta()) return(NextMethod()) # nocov | ||
| if (!cedta(verbose=FALSE)) return(NextMethod()) # nocov |
There was a problem hiding this comment.
What's the exact reason to forcing verbose to F here? Why in this particular method we want to see less?
There was a problem hiding this comment.
The reason is that we call dim in every print statement which are often not cedta
There was a problem hiding this comment.
Isn't that resolved by switching to nrow(x)[1L] in print.data.table?
We could instead call .Call(Cdim, x)[1L] right?
I do see other dim() usage in print.data.table:
data.table/R/print.data.table.R
Line 55 in 8f5ffa8
So maybe we want dim_x = .Call(Cdim, x) & proceed from there?
|
Yes, please revert changes to vignettes/fr/datatable-joins.Rmd |
I was getting the same thing leading to #7184, I guess if you revert and merge My understanding is we have some setting to auto-convert CRLF to LF, which shows up as a "ghost" editing the CRLF file & impossible to get around. Edit: I'm pretty sure it's our .gitattributes: Line 1 in 8f5ffa8 I'm not sure why that wasn't applied within GitHub. |
Hm, on the one hand such objects are kind of broken already, but I suppose they're found here and there. Maybe if (!cedta() && !is.null(df_dim <- NextMethod())) return(df_dim)
.Call(Cdim, x) |
|
That's because we have `* text eol=lf` in .gitattributes. You can try temporarily creating but not committing vignettes/.gitattributes with the contents `* -text` to tell Git to get out of your way for now.
|
please dont revert the work, several days have been spent to complete the task. Let us try on another product. Thanks. |
|
@ChristianWia thank you for your concern :) To be clear, the aim is only to revert the changes in this PR, which are spurious. The file in |

Closes #2422
But do not know how we should properly test this?