Ross Gayler

The root cause of this issue appears to be that `purl()` uses a heuristic string-matching method for processing calls to "read_chunk()". It is treating the chunk code as a string...

@yihui thanks for your rapid response. I think I had two problems: 1. My code broke `purl()` (because I assumed, incorrectly, that the chunk code was being syntactically analysed as...

Independently of whether the warning messages get displayed, I think it would be worth adding a warnings count (or logical) to skim_df for each variable in the input frame. I...

In Hadley Wickham's `readr` package all the problem reports (per row of input) are put in a data frame that is returned as an attribute of the output data frame...

I have just been working with a data set where skipping rows with NAs would be a very bad thing. For my problem domain an NA is better treated as...

@mexindian for my specific problem the right thing to do was treat NA as a wildcard that can match anything but doesn't increase your confidence in the match. My point...

I am just encountering this issue now (from a zero prior expertise base). I have checkmate assertions in my package code for argument checking and `testthat::expect_error()` in my unit testing....

Thanks @jdblischak I will have a look at https://github.com/pat-s/pathogen-modeling - but I think I will have to do that from a high-level-feels perspective rather than a code-I-can-steal-verbatim perspective because `{targets}`...

Thanks @jdblischak and @pat-s - I have so far only got as far as looking at https://github.com/pat-s/pathogen-modeling My uneducated reading of the code is as follows (my aplogies to @pat-s...

@jdblischak I am currently doing something like that with my {workflowr}-only workflow except that it tends to be a separate Rmd for each step in the pipeline (rather than each...