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 idiosyncracies. 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.
catchr on 2018-12-17.