-
Notifications
You must be signed in to change notification settings - Fork 76
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
.check_trust()
: Is there a way to NOT encouraging users to report the issue here?
#451
Comments
#452 I think we need to address this before the typical "semester beginning" wave. |
I think one solution is to not use |
Oh wow that's aggressive to report an issue to a maintainer when they've deprecated a feature? I'm good with swapping this to warning but that's a bad upstream choice. |
That is indeed a bit aggressive. I second that a good old warning is enough. |
Maybe should give this suggestion by @olivroy a try: r-lib/lifecycle#187 |
But how deep in the |
I think I still vote for an ordinary |
@schochastics OK, I agree with you. And I close this once again. |
Agreed the warning seems fine. Here is my attempt at explaining wjakethompson/taylor#49 (comment) This guide can be helpful too. https://rlang.r-lib.org/reference/topic-error-call.html I made a few PRs to implement this in different packages. See lintr for example r-lib/lintr#2602 or gt rstudio/gt#1638 |
rio/R/utils.R
Lines 145 to 150 in 447ea1b
The text was updated successfully, but these errors were encountered: