Skip to content

Consistently document JpaSpecificationExecutor to require non-null Specifications #2877

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.

Sign up for GitHub

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

Jump to bottom
Closed
mp911de opened this issue Mar 21, 2023 · 0 comments
Closed

Consistently document JpaSpecificationExecutor to require non-null Specifications #2877

mp911de opened this issue Mar 21, 2023 · 0 comments
Assignees
@mp911de
Labels
type: enhancement A general enhancement
Milestone
3.1 RC1 (2023.0.0)

Comments

@mp911de
Copy link
Member

mp911de commented Mar 21, 2023

JpaSpecificationExecutor currently has mixed nullability requirements and documentation for Specification. We should require non-null Specifications to have a consistent approach to specifications.
@mp911de mp911de added the type: enhancement A general enhancement label Mar 21, 2023
@mp911de mp911de added this to the 3.1 RC1 (2023.0.0) milestone Mar 21, 2023
@mp911de mp911de self-assigned this Mar 21, 2023
klajdipaja pushed a commit to klajdipaja/spring-data-jpa that referenced this issue Mar 24, 2023
@mp911de @klajdipaja
Consistently document JpaSpecificationExecutor to require non-null …
c2b58a8 
…`Specification`.

Closes spring-projects#2877
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mp911de mp911de

Labels
type: enhancement A general enhancement
Projects
None yet
Milestone
3.1 RC1 (2023.0.0)
Development

No branches or pull requests
1 participant
@mp911de