-
Notifications
You must be signed in to change notification settings - Fork 106
give .filter_eval_time() more informative warning #1043
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
Conversation
|
|
||
| cli::cli_warn( | ||
| c( | ||
| "There {?was/were} {diffs} inappropriate evaluation time \\ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤩
hfrick
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looove it! 😍 Does this break any snapshots in extratests?
| Condition | ||
| Warning: | ||
| There was 1 inappropriate evaluation time point that was removed. | ||
| There was 1 inappropriate evaluation time point that was removed. They were: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: They were -> It was. I'll add a suggestion!
Co-authored-by: Hannah Frick <hfrick@users.noreply.github.com>
|
i didn't test extratests because I still have a hard time making it run 😓 |
|
I searched the extratests snapshots and didn't see any matches to the old message. Either way, I seem to be updating the snapshots almost every 3h 😄 |
|
This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
To close #967
I went all in! it is super fancy now