blockchain2graph
blockchain2graph copied to clipboard
Bump mapstruct from 1.4.1.Final to 1.4.2.Final
Bumps mapstruct from 1.4.1.Final to 1.4.2.Final.
Release notes
Sourced from mapstruct's releases.
1.4.2.Final
Enhancement
- Relax strictness for
Mapping#qualifiedByNameandMapping#qualifierfor collection mappings (#2324, #2346)- Mark mapstruct-processor jar as Spring-Boot-Jar-Type: annotation-processor (#2244)
Bugs
- Nested target properties uses same method for different mappings after upgrade from 1.3.1.Final to 1.4.1.Final (#2236)
- MapStruct 1.3.0.Final version is generating wrong code for optional collection getter fields (#2233)
- Problems with
Optional<T>mapping (#2295)- Nested source null check calls method twice instead of using intermediate variable (#2245)
- Mapper create invalid implementation - variable is already defined in method (#2251)
- Stack Trace instead of Message on Missing Mapping (#2263)
- Wrong reporting for unmapped source properties when source source is implicitly mapped (#2253)
- Getting either "Unknown property" or "Unmapped target property" (#2301)
@InheritInverseConfigurationand@Mapping(target:"bean.childProperty", ignore=true)do not play together (#2278)- Mappings are ignored when
@InheritConfigurationdefines a mapping for a sub-field (#2318)Documentation
Commits
1ca7c7b[maven-release-plugin] prepare release 1.4.2.Final7d20cf2#2346 Update documentation and readme about MapStruct and Gradlebef3482#2250, #2324 Do not throw error when qualifier is missing on iterable mapping0c51f7a#2278 inherited property ignored due to ignore on nested level (#2332)15b3469#2301 Implicitly ignore forward inherited mappings from different method typese6479dc#2293 Use MapperConfig instead of MappingConfig in the documentation24ac2f3Update chapter-2-set-up.asciidoc164535eAdd Lombok subsection in the documentation (#2266)628ff17#2253 remove unmapped source properties when source parameter is directly mapped934d096#2263 Fix IndexOutOfBoundsException when resolving TypeVar to a Type- 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.
If all status checks pass Dependabot will automatically merge this pull request.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language -
@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
One of your CI runs failed on this pull request, so Dependabot won't merge it.
Dependabot will still automatically merge this pull request if you amend it and your tests pass.