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

JsonPathAssertions methods that take a type used as a lambda should be ordered consistently #32062

Closed
snicoll opened this issue Jan 19, 2024 · 0 comments
Assignees
Labels
in: test Issues in the test module type: enhancement A general enhancement
Milestone

Comments

@snicoll
Copy link
Member

snicoll commented Jan 19, 2024

There are several methods that take a Matcher or Consumer where the type won't be the last and that's not idiomatic as if you want to write a lambda, not having it the last argument is a little odd.

@snicoll snicoll added the type: enhancement A general enhancement label Jan 19, 2024
@snicoll snicoll added this to the 6.2.0-M1 milestone Jan 19, 2024
@jhoeller jhoeller added the in: test Issues in the test module label Jan 19, 2024
@snicoll snicoll self-assigned this Jan 19, 2024
snicoll added a commit to snicoll/spring-framework that referenced this issue Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: test Issues in the test module type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants