Jim Hester
Jim Hester
top level assignments are run when the package is built, e.g. during install time. covr measures what code is run during tests, this is not going to change.
``` r covr:::trace_calls(fun.list) #> $a #> function (x) #> { #> { #> covr:::count("0x404e048:3:5:3:14:5:14:3:3") #> y } #> { #> covr:::count("0x404e048:4:5:4:5:5:5:4:4") #> y #> } #> } #> #> $b...
The issue here is that currently the way covr works is to run `trace_calls()` on every object defined as a `function` in the package namespace. So in order to get...
I think you are correct, `name` and `env` are mainly there for debugging purposes, perhaps they should just be removed entirely.
@elinw if you want this fixed you need to provide links to the source of exactly what functions you think should have coverage, exact lines in the codecov report that...
We could maybe do it with a special comment as well, ideally your R code would not have to change.
One case where full traversal would like be problematic would be a data package using `LazyData`, pretty sure a full traversal would require all data objects to be loaded into...
I think in this case either the function is so trivial you don't need a test for it, or if you do want to test it a simpler way to...
Sure, sounds great to me!
Yes, R projects using covr are not affected by this because we do not use the bash uploader. I also just mentioned this in https://twitter.com/jimhester_/status/1382692471612833796