Refine Specification API #3578
Closed
Refine Specification API #3578
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mp911de
requested review from
christophstrobl,
schauder and
odrotbohm
and removed request for
christophstrobl
mp911de
force-pushed
the
main
branch
2 times, most recently
from
52ee55f to
61e6d36
Compare
|
LGTM |
schauder
approved these changes
Dec 19, 2024
| return (root, query, builder) -> { | ||
|
|
||
| Predicate not = spec.toPredicate(root, query, builder); | ||
| return not != null ? builder.not(not) : null; |
There was a problem hiding this comment.
That's so many not's, it's making knots in my brain. Could we at least reverse the comparison?
| static <T> Specification<T> anyOf(Iterable<Specification<T>> specifications) { | ||
|
|
||
| return StreamSupport.stream(specifications.spliterator(), false) // | ||
| .reduce(Specification.all(), Specification::or); |
There was a problem hiding this comment.
This looks really wrong to me. Specification.all() suggests a Specification that produces true for all inputs, which would always yield true when combined by OR with anything else.
I'd say the underlying problem is that all() is a misnomer. It should really be Specification.null() or Specification.empty(), shouldn't it?
There was a problem hiding this comment.
I updated the name to unrestricted() to express really what it does.
| public interface UpdateSpecification<T> extends Serializable { | ||
|
|
||
| /** | ||
| * Simple static factory method to create a specification deleting all objects. |
There was a problem hiding this comment.
I assume that should read "updating all objects"
| * @param spec must not be {@literal null}. | ||
| * @return guaranteed to be not {@literal null}. | ||
| */ | ||
| static <T> UpdateOperation<T> update(UpdateOperation<T> spec) { |
There was a problem hiding this comment.
Comments and error message talk about UpdateSpecification but the types used are UpdateOperation. I'm confused.
Introduce DeleteSpecification and UpdateSpecification. Add PredicateSpecification. Update SpecificationExecutor.
Gentle reminder to deprecate where before we remove it here
Revise nullability requirements around non-nullable specifications.
christophstrobl
added a commit
that referenced
this pull request
Jan 8, 2025
The where method will be removed with next major version containing some refinements in the Specification API. See: #3578
christophstrobl
added a commit
that referenced
this pull request
Jan 8, 2025
Also remove serialVersionUID. Original Pull Request: #3578
christophstrobl
pushed a commit
that referenced
this pull request
Jan 8, 2025
Revise nullability requirements around non-nullable specifications. Original Pull Request: #3578
christophstrobl
pushed a commit
that referenced
this pull request
Jan 8, 2025
Original Pull Request: #3578
christophstrobl
pushed a commit
that referenced
this pull request
Jan 8, 2025
Original Pull Request: #3578
mp911de
pushed a commit
that referenced
this pull request
Jan 14, 2025
Also remove serialVersionUID. Original Pull Request: #3578
mp911de
added a commit
that referenced
this pull request
Jan 14, 2025
Revise nullability requirements around non-nullable specifications. Original Pull Request: #3578
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduce
DeleteSpecificationandUpdateSpecification. AddPredicateSpecification. UpdateSpecificationExecutor.See #3521