This repository was archived by the owner on Oct 10, 2024. It is now read-only.
Open
Conversation
The builder pattern is nice, but it's frequent that you have some
conditional logic which forces you to interrupt the flow, assign
the builder to a temporary variable, do something on the builder,
then resume the fluent API like mode. A trivial example would be:
```java
TypeSpec.Builder typeBuilder = TypeSpec.classBuilder(...)
myMethods.forEach(typeBuilder::addMethod);
return typeBuilder.build()
```
This commit introduces a `tap` method on builders which avoids
the need of an intermediate variable by allowing to swich context
in a lambda, and apply the conditional logic (or more programmatic
work) within the lambda.
The code above would be rewritten as:
```java
return TypeSpec.classBuilder(...)
.tap(c -> methods.forEach(c::addMethod))
.build()
```
Which looks more functional style. Of course real world
examples the conditional logic is more complex ;)
Collaborator
|
This reminds me of |
Author
|
I don't know if there are other popular libraries using this pattern, but I've not seen many exposing builders like Javapoet does. From my point of view, I've been using Javapoet in pure Java for the past couple weeks and I've been annoyed several times that this method is not available. Of course you could say "use Kotlin" but it's a no-go: it would make the library too heavy for what it's doing. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The builder pattern is nice, but it's frequent that you have some
conditional logic which forces you to interrupt the flow, assign
the builder to a temporary variable, do something on the builder,
then resume the fluent API like mode. A trivial example would be:
This commit introduces a
tapmethod on builders which avoidsthe need of an intermediate variable by allowing to swich context
in a lambda, and apply the conditional logic (or more programmatic
work) within the lambda.
The code above would be rewritten as:
Which looks more functional style. Of course real world
examples the conditional logic is more complex ;)