Update dependency org.immutables:value-processor to v2.11.3 #38
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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
2.10.0
->2.11.3
Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
immutables/immutables (org.immutables:value-processor)
v2.11.3
Compare Source
Maintenance & refinements release
Thank you for PRs and providing feedback!
@Value.Default
, no warnings are issued.What's Changed
Full Changelog: immutables/immutables@2.11.2...2.11.3
v2.11.2
Compare Source
Maintenance and refinement release
from
merging method for many supertypesfrom
supertypes. Switch viaStyle.mergeFromSupertypesDynamically=false
. This gives (very) old behavior before dynamic merging was introduced, for some, it is more intuitive than dynamic logic and avoid heap pollution (& ClassCastException) for some rare cases of supertypes imlementing parameterized interfaces with different actual type arguments in a hierarchy.required=false
was generated only for Nullable, now - for any non mandatory attribute). Generating Jacksonrequired
can be disabled viasetJacksonPropertyRequired=false
, the difference is if Jackson will issue an error on missing attribute or Immutables' builder will throw an exception for the same.PRs merged
New Contributors
Full Changelog: immutables/immutables@2.11.1...2.11.2
v2.11.1
Compare Source
Maintenance and minor enhancements
static class Builder extends MyRecordBuilder {}
*IsSet
methods on builderorg.immutables:datatype
. It's slightly modernized version oforg.immutables:data
(now deprecated), no dependency on Guava, + support for records with generated buildersAlso
New Contributors
Full Changelog: immutables/immutables@2.11.0...2.11.1
v2.11.0
Compare Source
Many thanks to all contributors: PRs, testing and evaluation much appreciated!
@Value.Builder
for records on builders@Value.Default.*
annotation for constant default values for records and regular abstract types@Value.Builder record A(int a, String b) implements WithA {..
@Nullable
support in@NullMarked
mode.TYPE_USE
annotations (as far as compiler and peculiarities of existing code allows),Style.attributeBuilderDetection=true
:builder.value(b -> b.a(1).c(""))
Also
Closed issues https://github.com/immutables/immutables/milestone/82?closed=1
New Contributors
Full Changelog: immutables/immutables@2.10.1...2.11.0
v2.10.1
Compare Source
Maintenance release
What's Changed
New Contributors
Full Changelog: immutables/immutables@2.10.0...2.10.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.