Find source files with ParseExceptionResult markers
org.openrewrite.FindParseFailures
This 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.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite
artifactId: rewrite-core
version: 8.28.1
Options
Type | Name | Description | Example |
---|---|---|---|
| maxSnippetLength | Optional. 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 | Optional. Only display failures from parsers with this fully qualified name. |
|
| stackTrace | Optional. Only mark stack traces with a message containing this text. |
|
Data Tables
Parser failures
A list of files that failed to parse along with stack traces of their failures.
Column Name | Description |
---|---|
Parser | The parser implementation that failed. |
Source path | The file that failed to parse. |
Exception type | The class name of the exception that produce the parse failure. |
Tree type | The type of the tree element that was being parsed when the failure occurred. This can refer either to the intended target OpenRewrite Tree type or a parser or compiler internal tree type that we couldn't determine how to map. |
Snippet | The code snippet that the failure occurred on. Omitted when the parser fails on the whole file. |
Stack trace | The stack trace of the failure. |
Usage
This recipe has no required configuration parameters and comes from a rewrite core library. It can be activated directly without adding any dependencies.
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
Shannon Pamperl, Jonathan Schnéider, Tracey Yoshima, Knut Wannheden, Tim te Beek, Mike Solomon
Last updated