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

Don't fire PreferJavaTimeOverload on custom AssertJ assertThat() overloads. #1436

Closed

Conversation

carterkozak
Copy link
Contributor

Fixes #1435
Related to #1377 and f1df86d

@carterkozak
Copy link
Contributor Author

it's unfortunate there is no dependency on assertj, writing a test is difficult.

@barorion
Copy link

barorion commented Dec 8, 2019

org.assertj.core.api.BDDAssertions is a BDD style variant of org.assertj.core.api.Assertions. It's assertion method is then() (instead of assertThat()).
PreferJavaTimeOverload should probably be muted for it too...

@kluever kluever self-assigned this Dec 9, 2019
cgdecker pushed a commit that referenced this pull request Dec 9, 2019
@cgdecker cgdecker mentioned this pull request Dec 9, 2019
cgdecker pushed a commit that referenced this pull request Dec 9, 2019
kmclarnon pushed a commit to HubSpot/error-prone that referenced this pull request Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PreferJavaTimeOverload fails on AssertJ extensions which handle time
4 participants