skuzzle / restrict-imports-enforcer-rule

Gradle plugin & Maven Enforcer rule that restricts usage of unwanted imports in Java, Kotlin and Groovy source files.
MIT License
75 stars 12 forks source link

Bump equalsverifier from 3.14.3 to 3.15 #91

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps equalsverifier from 3.14.3 to 3.15.

Release notes

Sourced from equalsverifier's releases.

Release equalsverifier-3.15

For a list of changes in this version, see CHANGELOG.md.

Changelog

Sourced from equalsverifier's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Changed

  • Check that getters are used for all mapped fields in JPA entities, not just the ones with FetchType.LAZY. (Issue 830)Note that this is a breaking change for JPA entity tests. This can be disabled by suppressing Warning.JPA_GETTER. See the manual page about JPA entities, specifically the section on Materialized fields, for more details.

Added

  • #withFieldnameToGetterConverter() to override the derivation of getter names from field names when testing JPA entities. (Issue 829)
  • Warning.JPA_GETTER to suppress the check that getters should be used instead of direct field references in JPA entities.
Commits
  • a4d3541 Bumps version to 3.15
  • aaa9d60 Merge pull request #837 from jqno/entity-lazy-fields
  • 2f3f538 Updates CHANGELOG for new behaviour around JPA entities
  • 22ed6f5 Adds error message explained for JPA Getter error
  • 2f1f85d Adds section on materialized fields in documentation
  • 053eefd Adds tests for Jakarta lazy fields
  • 0fdbd43 Adds Warning.JPA_GETTER
  • 41c219c Requires getters for JPA collection fields even if they're not lazy
  • 80b0360 Propagates fieldnameToGetter via ConfiguredEqualsVerifier
  • 2fad0ea Allow different field and getter method naming standards
  • Additional commits viewable in compare view


Dependabot compatibility score

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)