-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Feature request: Unify order of parameters #2173
Comments
No, this might be a simple oversight. @raphw I think we can reverse the order? We would need to add an overload and then deprecate the existing one, which we can delete in Mockito 4.0.0. |
No, I don't think I had an intention with the order, possibly to have the lambda last what often works better with languages like Kotlin. But I think consistency is the better goal. |
@bohni Do you mind sending us a PR with the added method + deprecation? |
OK, I will take a look |
For consistency, the parameters of the method `MockedStatic.verify(VerificationMode, Verification)` have been swapped to `MockedStatic.verify(Verification, VerificationMode)` as this order is already used in `Mockito.verify(T, VerificationMode)`. Fixes: #2173 [ci maven-central-release]
Hello,
I just stumbled accross the switched order of the VerificationMode parameter
vs
Is there a reason, the VerificationMode from MockitoStatic is at first position?
The text was updated successfully, but these errors were encountered: