Issue/2761 specifications with from

[svenmeier]

Proposal for GH-2761

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[mp911de]

For 4.0, we've introduced PredicateSpecification for improved composition, therefore, we don't want to include another nestable specification. The Join-specification seems rather specific and given the improved flexibility with From, we do not want to introduce another specification variant.

[Farley-Chen]

For 4.0, we've introduced PredicateSpecification for improved composition, therefore, we don't want to include another nestable specification. The Join-specification seems rather specific and given the improved flexibility with From, we do not want to introduce another specification variant.

Hi, I have found that in PredicateSpecification there is still using Root, is there any plan or solution to use From for join purpose ?

[mp911de]

Good point @Farley-Chen. We've revised PredicateSpecification by apply <T> to From<?, T> for improved composition. While we lose a bit of type information, we also drop our opinion on type restrictions and open up the model for improved composition and reuse across e.g. Joins.