Open andersone1 opened 8 months ago
I like this idea @andersone1 . @barrettk has also been messing around with some nicer formatting for error messages (#624 for example). Notably, this can call attention to things that the user should act on right away, as opposed to more verbose output that is more helpful for debugging.
A few notes after reviewing this with @barrettk
{getOption('bbr.bbi_exe_path')}
bbr::use_bbi()
to install bbi or ...options('bbr.bbi_exe_path' = '/path/to/bbi')
Current behavior when a
bbr
function is run on a system withoutbbi
installed:Can we append how to install
bbi
to this error message (and be more specific about where it is being looked for), making it something like: