Add column of "trace_source"

[mpadge]

With value of either "examples" or "tests". For ropensci-review-tools/autotest#76

[mpadge]

Re-opened because this extra column has to be put in the tracing template too, to ensure consistent trace structure. At present, traces created from packages have this column, but traces from functions do not.

[mpadge]

Nope, not quite. Still some buggy behaviour with capturing the correct calling environment

[mpadge]

Here is the output applied to a modified version of geodist which has one example wrapped in tryCatch.

library (typetracer)
packageVersion ("typetracer")
#> [1] '0.1.1.37'
path <- "/<path>/<to>/hypertidy/geodist"
res <- trace_package (pkg_dir = path)
table (res$call_env)
#> 
#>               base::lapply             base::tryCatch 
#>                         56                          4 
#>           geodist::geodist geodist::geodist_benchmark 
#>                        560                          6 
#>       geodist::geodist_min       geodist::geodist_vec 
#>                         20                        180 
#>          geodist::georange     testthat::expect_error 
#>                        100                         58 
#>   testthat::expect_message    testthat::expect_silent 
#>                         82                         41

^{Created on 2023-06-22 with reprex v2.0.2}

(Note that this doesn't actually work in reprex, because that uses a fresh environment which strips all typetracer injections. This has been lightly faked.)

And the "call_env" column enables identication of function calls which are made under various expections, importantly including try/tryCatch, and all testthat::expect_ functions. Those can then be ignored in autotest to finally capture only calls expected to succeed, and so properly trace acceptable parameter types 🚀 🍾