- I incorporated a push request from Lionel (lionel-) due to a change in
rlang. catchr should work with newer versions ofrlangfrom now on. - I made catchr throw an error if plans are made with
beepandbeepris not installed. This was expected by the unit tests, but not implemented. - I fixed some boilerplate stuff so CRAN wouldn't complain.
- I updated some presentational stuff and made some minor fixes to the package (non-functional changes).
- I hate to waffle on features, but I realized that treating expressions with the
!!and!!!operators differently in catchr doesn't make as much sense to me as it did before. (I honestly can't see why I ever even allowed this behavior.) The use-case Stephen (yogat3ch) pointed out made this clear, so expressions with these operators are now treated like normal expressions. This is basically a reverse of the previous0.2.2patch, but on reflection, I think it makes more sense to do it this way.
I added quasiquotation capabilities to catchr::catch_expr() and catchr::make_catch_fn(), letting you unquote with the tidyverse's !! and !!! functions. Hopefully this doesn't break anything---it hasn't caused any errors in my tests or code so far, but if you have something weird happen, try version 0.2.1 and report the bug fix on GitHub.
- The warning about catchr's DSL terms potentially masking some variables no longer has a typo.
- catchr no longer warns the user about
user_exit()/user_display()being top level if they're within a function.
Removed with_ordered_handlers since it was essentially a gimmick anyway, and because it doesn't feel worth it to keep up with whatever rlang's current idiomatic handler framework is at any given moment.
Fixed some breaking changes from rlang updating to version 0.4.0, primarily with rlang::fn_fmls() and rlang::with_handlers(). catchr::with_ordered_handlers() should be viewed suspiciously, as it hasn't been vetted with the new rlang::with_handlers code.
Unfortunately, since rlang v0.4.0 has stopped supporting versions of R below v3.2.0, so has catchr. To use catchr with older versions of R, use catchr v0.2.0 with rlang v0.3.1.
summarynow works correctly oncatchr_compiled_plans, rather than throwing an error.
This version of catchr is essentially a new package---consider all previous functions to be hard-deprecated, and there to be zero backward-compatibility. These huge, package-breaking changes were made while catchr was very young and had few (if any) users. Moving forward, there will be a (normal) emphasis on backward-compatibility, and such drastic changes are unlikely to ever happen again. The version number was only incremented by 0.1.0 to avoid the implication that this package is feature complete with a stable API.
Instead of listing everything in the package, check out the introductory vignette and help documentation for new features.
R has a unique way of dealing with warnings, errors, messages, and other conditions, but it can often be troublesome to users coming from different backgrounds. Starting from the idea that it should be more flexible and generative, the code now lets users generate their own "catching" functions where they can specify the behavior via conceptual "plans".
In order to lower the barrier of entry, keep code clean and readable, and reduce the amount of typing required, catchr now uses a very simple domain-specific language that simplifies things on the front-end. catchr's aim is to maintain a continuous learning curve that lets new users jump straight in to condition-handling, while simultaneously offering depth and complexity for more advanced users.
catchr now depends on a few packages. Much of the functions in catchr v0.1.0 were redundant with functions from rlang; now catchr leans heavily on this package to bring simplicity to users less familiar with R's condition-handling idiosyncrasies. For convenience, it uses a few functions from purrr as well. It also suggests beepr and crayon for extra functionality in the auditory and visual domains, respectively.
- Original GitHub release of
catchron 2018-12-17.