Find source files with ParseExceptionResult markers
Recipe ID
org.openrewrite.FindParseFailuresArtifact
org.openrewrite:rewrite-coreThis recipe explores parse failures after an LST is produced for classifying the types of failures that can occur and prioritizing fixes according to the most common problems.
Usage
This recipe has no required configuration options. You’ll need the Moderne CLI configured before running the command below.
mod run . --recipe org.openrewrite.FindParseFailuresIf the recipe isn’t available locally, install it with:
mod config recipes jar install org.openrewrite:rewrite-core:8.88.0Options
| Name | Type | Description |
|---|---|---|
maxSnippetLength | Integer | When the failure occurs on a granular tree element, its source code will be included as a column in the data table up to this maximum snippet length. |
parserType | String | Only display failures from parsers with this simple name. e.g. YamlParser |
stackTrace | String | Only mark stack traces with a message containing this text. e.g. RuntimeException |
createdAfter | String | Only report on source files that were created after this date. e.g. 2025-01-01 |
Data tables
Structured output this recipe can produce.
- Parser failuresA list of files that failed to parse along with stack traces of their failures.
org.openrewrite.table.ParseFailures - Source files that had resultsSource files that were modified by the recipe run.
org.openrewrite.table.SourcesFileResults - Source files that had search resultsSearch results that were found during the recipe run.
org.openrewrite.table.SearchResults - Source files that errored on a recipeThe details of all errors produced by a recipe run.
org.openrewrite.table.SourcesFileErrors - Recipe performanceStatistics used in analyzing the performance of recipes.
org.openrewrite.table.RecipeRunStats