Brodie Gaslam
Brodie Gaslam
Main complication is to figure out if there is a way to automatically use diffobj if it is available without requiring at a minimum a `suggests` dependency. We really need...
Right now they're controlled all over the place, for diffobj output, for comments, and for test status in test browse listing. If any other places end up using color it...
Currently not entirely sure when `on.exit` would get called. Maybe after eval of that same expression? Based on this it would seem so: ``` > eval(quote(on.exit(cat('hello\n')))) hello ``` If so...
e.g. in `alike(x=1)` using `editCalls(..., quote(x), quote(y))` won't do anything.
Would need good references (e.g. `untz015>` at the prompt), and the ability to easily get to browse to that test (e.g. "q" to exit pager, then "B015" or some such...
Typical scenario is: 1. run unitize_dir 2. one of the files has errors, all others pass 3. view errors, fix source, hit R 4. on re-evaluation, success so taken back...
``` # Failed test #1: for non-existent paths, `pretty_path` is expected to return # the input. Internally, it calls `normalizePath(..., mustWork=FALSE)`, which # is likely returning the full path to...
Unfortunately, all our classes are lowerCamelCase, when they should be UpperCamelCase, with only methods in LowerCamelCase. This is going to be a PITA to change so we'll probably never fix,...
Maybe even make it part of the prompt? ``` #043> ```