AshesITR
AshesITR
That means no todo for lintr: ``` r tmp [1] TRUE length(lintr::lint(tmp)) #> [1] 0 ``` Created on 2022-07-11 by the [reprex package](https://reprex.tidyverse.org) (v2.0.1)
Related: Is there a legitimate use for 0-byte chunks? If not, maybe lint them too?
Ah, yes, the `child` chunk arg is definitely a valid use case. Over all, I think empty chunks should not contain blank lines to emphasize their speciality. Using Ctrl +...
@jimhester provided some guidance as to how this could be done: https://github.com/r-lib/lintr/issues/824#issuecomment-1162132723
Can you check if this issue occurs in the master branch? I can't reproduce with that.
I like your suggestion, but would leave out the "is risky" part. > Mixing `:` with `nrow` is prone to errors when `nrow` is 0.
We currently produce check annotations, and support error_on_lint to exit if a lint is found. Maybe we can default `error_on_lint` to `in_ci()`?
The particular instance could be fixed if comments within comments were ignored in the test for code candidates. Maybe `parseable()` could be refactored to `codeish()` and check whether the parsed...
I found it a very common beginner mistake among my colleagues - especially if not used to the wonders of git being capable of resurrecting every line of code if...
Not sure about the .R extension. Most IDEs allow you to configure the default language per extension, and that makes it easy to confuse the config with an actual (productive)...