Recipes

Composite Recipes

Recipes that include further recipes, often including the individual recipes below.

• Java Recipe best practices
• Recipe nullability best practices
• Recipe testing best practices
• Use StringUtils utility methods

Recipes

• Add a blank line around fields with annotations
• Automatically select recipe examples from the unit test cases of a recipe
• Correctly spaced descriptions
• Extract documentation examples from tests
• Find OpenRewrite recipes
• Find missing @Option example values
• Generate InlineMethodCalls recipes for deprecated delegating methods
• Make declarative recipes singletons
• Migrate tests to Java 21
• Minimal indentation for SourceSpecs text blocks
• New line at the end of SourceSpecs text blocks
• Recipe classes should be public
• Recipe classes should not have mutable static fields
• Refactor RewriteTest to use defaults method
• Remove @NlsRewrite annotations from Recipe classes
• Remove elements annotated with @ToBeRemoved past their date
• Reorder maybeRemoveImport before maybeAddImport
• Replace getDisplayName() and getDescription() methods with fields
• Replace getEstimatedEffortPerOccurrence() method with field
• Replace getTags() method with field
• Replace null with RewriteTest.doesNotExist()
• RewriteTest classes should not be public
• Show @DocumentExamples first
• Single @DocumentExample per test class
• Use !StringUtils#isBlank(String)
• Use J.Literal.isLiteralValue(expression, null)
• Use JavaTemplate.apply() static method
• Use StringUtils#isBlank(String)
• Use StringUtils#isNotEmpty(String)
• Use StringUtils#isNullOrEmpty(String)
• Use Tree.randomId() in LST constructors
• Use a standard name for ExecutionContext
• Use of @EqualsAndHashCode on Recipe
• Use visit with parent cursor when calling from another visitor