June Choe

Thanks for the patience! This is now supported in devel. `columns = vars(a)` and `columns = c(a)` are identical sans the captured user expression: ```r agent `old$validation_set$columns_expr`: "vars(a)" #> `new$validation_set$columns_expr`:...

Hi - just wanted to check in on this since I see it tagged for the next version milestone! If I understand correctly, the initial issue about yaml writing seems...

Sounds good to me! I also don't have strong feelings on the remaining items (they seem isolated enough to get fixed in later patch versions). I only selfishly want to...

While we *could* try to make this work with some automagic, my preference would be for the user to simply define the function *outside* of the `preconditions` argument (where you...

> better to not promise anything, than promising and not delivering Well put - that's the conclusion that I'm circling back to as well. Maybe once `I()` gets more widely...

Got it - that sounds completely reasonable! I'm content with just the fact that this is clarified for me - I'll let you make the call for whether this also...

Hi! Just wanted to bump this with a similar issue for nesting `\dontshow{}` in `\donttest{}`. This is common when examples have setup code you want to hide (API auth, establishing...

Thanks @gkaramanis! You're totally right about the different behavior of height/width for gt tables - I hadn't thought it through that far so good catch 😅 As you say it's...

Fixed in dev! ```r agent % create_agent() %>% col_vals_expr(expr(x + y == z)) %>% interrogate() get_agent_report(agent) ```  ```r get_agent_report(agent, display_table = FALSE)$columns #> [1] "x, y, z" ```

Apparently `{covr}` injects its own expressions into even `quote()`/`expr()`-ed code - https://github.com/r-lib/covr/issues/381. This unfortunately interferes with the expr parsing process and makes the new feature impossible to test on the...