Use the builder pattern where possible
org.openrewrite.staticanalysis.UseAsBuilder
When an API has been designed as a builder, use it that way rather than as a series of setter calls.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.recipe
artifactId: rewrite-static-analysis
version: 1.5.0
Options
Type | Name | Description | Example |
---|---|---|---|
| builderType | Fully qualified name of the Builder |
|
| immutable | Optional. The builder is immutable if you must assign the result of calls to intermediate variables or use directly. Defaults to true as many purpose-built builders will be immutable. | |
| builderCreator | Optional. The method that creates the builder instance, which may not be a method of the builder itself. |
|
Usage
This recipe has required configuration parameters. Recipes with required configuration parameters cannot be activated directly. To activate this recipe you must create a new recipe which fills in the required parameters. In your rewrite.yml
create a new recipe with a unique name. For example: com.yourorg.UseAsBuilderExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.UseAsBuilderExample
has been defined activate it and take a dependency on org.openrewrite.recipe:rewrite-static-analysis:1.5.0 in your build file:
Add the following to your
build.gradle
file:
Run
gradle rewriteRun
to run the recipe.
See how this recipe works across multiple open-source repositories
The community edition of the Moderne platform enables you to easily run recipes across thousands of open-source repositories.
Please contact Moderne for more information about safely running the recipes on your own codebase in a private SaaS.
Contributors
Last updated