Finds flow between two methods
org.openrewrite.analysis.search.FindFlowBetweenMethods
Takes two patterns for the start/end methods to find flow between.
Recipe source
GitHub, Issue Tracker, Maven Central
groupId: org.openrewrite.meta
artifactId: rewrite-analysis
version: 2.6.0
Options
Type | Name | Description | Example |
---|---|---|---|
| startMethodPattern | A method pattern that is used to find matching the start point's method invocations. |
|
| startMatchOverrides | Optional. When enabled, find methods that are overrides of the method pattern. | |
| endMethodPattern | A method pattern that is used to find matching the end point's method invocations. |
|
| endMatchOverrides | Optional. When enabled, find methods that are overrides of the method pattern. | |
| target | The part of the method flow should traverse to Valid options: | |
| flow | When enabled, show the data or taint flow of the method invocation. Valid options: |
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.FindFlowBetweenMethodsExample
. Here's how you can define and customize such a recipe within your rewrite.yml:
Now that com.yourorg.FindFlowBetweenMethodsExample
has been defined activate it and take a dependency on org.openrewrite.meta:rewrite-analysis:2.6.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.
Last updated