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

use expect_null where appropriate #6211

Merged
merged 1 commit into from
May 24, 2022

Conversation

MichaelChirico
Copy link
Contributor

Surfaced by the new lintr::expect_null_linter().

Filing wondering:

And also looking for feedback on how appropriate the lint is for usages in CRAN packages. Thanks.

Copy link
Member

@romainfrancois romainfrancois left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

MichaelChirico added a commit to MichaelChirico/dplyr that referenced this pull request Mar 22, 2022
Similar to tidyverse#6211 -- caught with `lintr::expect_type_linter()`.
@DavisVaughan DavisVaughan merged commit 778ec9b into tidyverse:main May 24, 2022
@DavisVaughan
Copy link
Member

Thanks @MichaelChirico!

DavisVaughan pushed a commit to MichaelChirico/dplyr that referenced this pull request May 24, 2022
Similar to tidyverse#6211 -- caught with `lintr::expect_type_linter()`.
DavisVaughan pushed a commit that referenced this pull request May 24, 2022
* Use expect_type where appropriate

Similar to #6211 -- caught with `lintr::expect_type_linter()`.

* one more
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants