You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While it's convenient to list recipes we want to apply on the command line, this approach may become cumbersome when dealing with numerous recipes (10 or more).
Based on my experience with OpenRewrite 6 months ago, I'd like to propose a more structured approach:
Context-Specific Recipe Sets:
Shortly after, I found a need for assembling specific recipes based on:
The plugin's current state (e.g., vastly outdated, needing JDK8 migration)
The goal we're pursuing
Cookbook Concept:
We could create a "cookbook" that references predefined recipes. For example, we could have a set of recipes corresponding to the "Improve a Plugin" tutorial.
Command Line Enhancement:
We should consider adding an option to distinguish between a recipe list and a cookbook list in the command line interface.
What are your thoughts on this approach? Do you see any potential challenges or benefits?
I'm particularly interested in:
The feasibility of implementing a cookbook system
How this might improve our workflow
Any alternative approaches we should consider
Thank you for your input.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered:
I think it's the next "big" feature we need to work on.
Right now the list of recipe on the recipes.yml is quiet flat and some recipes are refined at top level to avoid code duplication.
But some of those recipes like io.jenkins.tools.pluginmodernizer.RemoveExtraMavenProperties are not supposed to be called directly. Because they assume that a bom is present to remove some property. The original remove (https://docs.openrewrite.org/recipes/maven/removeproperty) doesn't check if the property is used on the pom or tree.
So I'm not sure how to expose this "cookbook", if we need some high level concept on top of recipes. Or if using tags on recipes that should be available on top level is enough
What feature do you want to see added?
While it's convenient to list recipes we want to apply on the command line, this approach may become cumbersome when dealing with numerous recipes (10 or more).
Based on my experience with OpenRewrite 6 months ago, I'd like to propose a more structured approach:
Recipe Catalog:
Six months ago, I created a list of all the recipes I was interested in.
Context-Specific Recipe Sets:
Shortly after, I found a need for assembling specific recipes based on:
Cookbook Concept:
We could create a "cookbook" that references predefined recipes. For example, we could have a set of recipes corresponding to the "Improve a Plugin" tutorial.
Command Line Enhancement:
We should consider adding an option to distinguish between a recipe list and a cookbook list in the command line interface.
What are your thoughts on this approach? Do you see any potential challenges or benefits?
I'm particularly interested in:
Thank you for your input.
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: