-
Notifications
You must be signed in to change notification settings - Fork 186
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
New stop_paste_linter #999
Conversation
# Conflicts: # man/linters.Rd
Maybe call it |
However I have some gut feeling about why we didn't do that in the first place... can't place exactly why. I will run an updated linter that catches |
cat(">", letters, "<")
# > a b c d e f g h i j k l m n o p q r s t u v w x y z < This means |
Good point... so I guess it might be a bit muddled to include that in the same linter. What about |
Sounds too unfamiliar I think. What about BTW: |
I'd been specifically shying away from "message" because
I think that's probably the way to go. "condition" as an adjective helps make clearer that it's not just |
# Conflicts: # DESCRIPTION # NAMESPACE # inst/lintr/linters.csv # man/best_practices_linters.Rd # man/consistency_linters.Rd # man/linters.Rd
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.
LGTM apart from the doc problem.
# Conflicts: # DESCRIPTION # NAMESPACE # inst/lintr/linters.csv # man/best_practices_linters.Rd # man/linters.Rd
Should we |
Part of #962
This one could probably go for an improved name as well, but I am consistently stumped here.