-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QC: replace stop()
with rlang::abort()
throughout package
#1976
Comments
|
yeah, i was going off of devin's comment, but sort of think it makes sense to use cli formatting in a log4r fatal log per zelos' work. happy to come up with a solution that makes the most sense here in the comments |
I believe I wrapped both "ERROR" and "FATAL" in logger as |
How do we feel about the:
Should we create some sort of assert/stop wrapper along the lines of:
it would collapse these calls and use the log4r setup we have? |
stop_if_not <- function(condition, message) {
stop_if(!condition, message)
} |
Love it. |
QC Details
use
rlang::abort()
instead ofstop()
for fatal errors so that it can provide more information, rather than just the message. See this for more information on the differencesAdditional Comments
The text was updated successfully, but these errors were encountered: