Skip to content
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

Does deprecate_stop() need a call argument? #156

Open
DavisVaughan opened this issue Jan 13, 2023 · 0 comments
Open

Does deprecate_stop() need a call argument? #156

DavisVaughan opened this issue Jan 13, 2023 · 0 comments
Labels
feature a feature request or enhancement

Comments

@DavisVaughan
Copy link
Member

Probably related to #131

It seems like the function that caused the error is never actually shown in the error message. I was expecting to see Error in fn(): here.

Is the env argument enough? Or do we need call separately?

fn <- function() {
  lifecycle::deprecate_stop(
    when = "1.0.0",
    what = I("Supplying `...` without names"),
    details = "foo"
  )
}

fn()
#> Error:
#> ! Supplying `...` without names was deprecated in <NA> 1.0.0 and is now
#>   defunct.
#> ℹ foo
@hadley hadley added the feature a feature request or enhancement label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a feature request or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants