add support for mandatory parameters #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds two new fields on the @option annotation to configure whether or not a parameter is required during the instantiation of the builder (to fix a set of immutable parameters) or during the creation of the object to be build (to enforce providing mandatory parameters). In case of conflicting configuration, e.g. when a default value is specified simultaneously, a warning is logged and the annotation processor gracefully prefers the attributes during instantiation/creation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds two new fields on the
@Optionannotation to configure whether or not a parameter is required during the instantiation of the builder or during the creation of the object to be built.In combination with the fix for successfully suppressing the generation of
get/set/withmethods, this allows preconfiguring a builder with a set of immutable parameters and/or enforce the user to provide mandatory parameters at creation time.In case of a conflicting configuration, e.g. when a default value is specified simultaneously, a warning is logged and the annotation processor gracefully prefers the attributes during instantiation/creation.
This feature is fully backwards-compatible, as this additional functionality is disabled by default and hence behaves like the current/latest version.