Bump specification-arg-resolver from 2.6.2 to 3.0.1

[dependabot]

Bumps specification-arg-resolver from 2.6.2 to 3.0.1.

Release notes

Sourced from specification-arg-resolver's releases.

v3.0.1

Changelog:

• Fixed a bug related to specifications that always returned all available values. Fixed specs:
  • InThePast
  • InTheFuture

v3.0.0

Changelog:

• Migrated project to spring boot 3.0 and java 17
  • Spring boot 3.0 is based on Hibernate version 6.X because in this version of hibernate all query results are distinct by default. This shouldn't affect most projects, but please be extra careful if you've ever used a spec with the distinct=false attribute.
• Added support for spring native-image.
  • Specification-arg-resolver can be used in GraalVM native images, but it requires several additional configuration steps. This is due to the fact that this library relies on Java reflection heavily. Please see https://github.com/tkaczmarzyk/specification-arg-resolver/blob/HEAD/README_native_image.md for the details
• Modified Springdoc-openapi dependency to be compatible with spring boot 3.0
• Refactored IsMember, IsNotMember specifications - they no longer use reflection explicitly.
• changed default join type in @Join from INNER to LEFT. I.e. if you have been using @Join with default join type:

  @Join(path="addresses", alias="a")

  Then, if you want to keep INNER join behaviour, you need to make it explicit (otherwise it will be LEFT):

  @Join(path="addresses", alias="a", type=JoinType.INNER)

• Changed join lazy evaluation:
  • Inner joins are now evaluated even if there is no filtering applied on the joined part due to a missing HTTP param (as inner join may narrow down query results)
  • For non-distinct queries, all joins are now evaluated eagerly (even if there is no filtering applied on the joined part). Reminder for Hibernate users: from Hibernate 6 onwards, all queries are distinct anyway
  • in all other situations, left and right joins are not evaluated unless there is filtering on the joined part (and the corresponding HTTP param is present)
• Removed all deprecated items, including:
  • DateAfter, DateAfterInclusive, DateBefore, DateBeforeInclusive - use GreaterThan, GreaterThanOrEqual, LessThan or LessThanOrEqual
  • DateBetween - use Between
  • EqualEnum - use Equal
  • @Joins container annotation - use repeated @Join and @JoinFetch

v2.18.1

• Fixed a bug related to specifications that always returned all available values. Fixed specs:
  • InThePast
  • InTheFuture

v2.18.0

Changelog:

• IsNull specification is no longer deprecated
• Introduced IsNotNull specification.

v2.16.0

Changelog:

• Introduced EqualDay specification which allows finding all records within particular date (day), ignoring time.
• Added ability to set custom Locale during resolver registration:

  @Override
  public void addArgumentResolvers(List<HandlerMethodArgumentResolver> argumentResolvers) {
      argumentResolvers.add(new SpecificationArgumentResolver(new Locale("pl", "PL"))); // pl_PL will be used as the default locale

... (truncated)

Changelog

Sourced from specification-arg-resolver's changelog.

v3.0.1

• Fixed a bug related to specifications that always returned all available values. Fixed specs:
  • InThePast
  • InTheFuture

v3.0.0

• Migrated project to spring boot 3.0 and java 17
  • Spring boot 3.0 is based on Hibernate version 6.X because in this version of hibernate all query results are distinct by default. This shouldn't affect most projects, but please be extra careful if you've ever used a spec with the distinct=false attribute.
• Added support for spring native-image.
  • Specification-arg-resolver can be used in GraalVM native images, but it requires several additional configuration steps. This is due to the fact that this library relies on Java reflection heavily. Please see https://github.com/tkaczmarzyk/specification-arg-resolver/blob/master/README_native_image.md for the details
• Modified Springdoc-openapi dependency to be compatible with spring boot 3.0
• Refactored IsMember, IsNotMember specifications - they no longer use reflection explicitly.
• changed default join type in @Join from INNER to LEFT. I.e. if you have been using @Join with default join type:

  @Join(path="addresses", alias="a")

  Then, if you want to keep INNER join behaviour, you need to make it explicit (otherwise it will be LEFT):

  @Join(path="addresses", alias="a", type=JoinType.INNER)

• Changed join lazy evaluation:
  • Inner joins are now evaluated even if there is no filtering applied on the joined part due to a missing HTTP param (as inner join may narrow down query results)
  • For non-distinct queries, all joins are now evaluated eagerly (even if there is no filtering applied on the joined part). Reminder for Hibernate users: from Hibernate 6 onwards, all queries are distinct anyway
  • in all other situations, left and right joins are not evaluated unless there is filtering on the joined part (and the corresponding HTTP param is present)
• Removed all deprecated items, including:
  • DateAfter, DateAfterInclusive, DateBefore, DateBeforeInclusive - use GreaterThan, GreaterThanOrEqual, LessThan or LessThanOrEqual
  • DateBetween - use Between
  • EqualEnum - use Equal
  • @Joins container annotation - use repeated @Join and @JoinFetch

v2.18.1

• Fixed a bug related to specifications that always returned all available values. Fixed specs:
  • InThePast
  • InTheFuture

v2.18.0

• IsNull specification is no longer deprecated
• Introduced IsNotNull specification.

v2.17.0

• Introduced converter for char primitive and Character class
• Introduced new specifications:
  • isEmpty, isNotEmpty - these specifications filter out elements that have empty (not empty) collection of elements, that is defined under path in @Spec annotation.
  • Empty - this specification filters for collections using is empty or is not empty, depending on the value of the parameter passed in (e.g. where customer.orders is empty).
  • NotEmpty - it is a negation for Empty specification.

... (truncated)

Commits

• e8a4a7b [maven-release-plugin] prepare release v3.0.1
• 304ab9f Added maven surefire plugin configuration (#227)
• 75bfef2 Upgraded junit version (junit4 => junit5) (#226)
• 49cfcba Fixed InTheFuture and InThePast specifications (#223)
• 23e262e Added Calendar e2e tests and EqualDay specification tests (#217)
• b86d144 Bump spring-boot-dependencies from 3.0.0 to 3.0.2 (#221)
• d925246 Bump classgraph from 4.8.151 to 4.8.154 (#222)
• 73ca15d v3.0.0 in README.md
• 0bf86f0 [maven-release-plugin] prepare for next development iteration
• 224df43 [maven-release-plugin] prepare release v3.0.0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)