Functionallity brainstorming

[AB-xdev]

ℹ️ = Non primary goal idea

• Executing recipes
  • Triggers:
  • Menu bar > Tools > OpenRewrite > Run recipe...
  • Right click a project > OpenRewrite > Run recipe...
  • Dialog with multiple sites (Next) shows up
  • If possible: Non modal
  • Sites:
    1. Select the recipe to run
       • Multiple options:
       • ℹ️ Use Marketplace
         • Requires login
         • Requires resolution of maven artifacts
         • Enhances below option
       • Enter maven artifact + Recipe directly
       • ℹ️ Enter recipe manually (may require maven artifact location)
         • Useful when executing multiple recipes (copy paste from marketplace recipe builder)
       • ℹ️ Enter parameters - if required
         • Will likely require some kind of inspection (because there might be Java annotations)
       • ℹ️Display/Explain what the recipe/s do
       • Maybe similar to GitHub actions?
    2. Select to project to execute this recipe on
       • Maybe also allow external projects that are located somewhere else on the disk
       • Should be automatically filled in when started from "Right click a project"
• ℹ️ Writing recipes
  • Auto completion support
  • Execute the written recipe for another project (e.g. test project)
  • Similar to Executing recipes above

[JohannesRabauer]

I would completely kill the idea of "Writing recipes". That is a nightmare and we shouldn't be involved in that. The Using-Part is much more in demand IMHO.

A feature i would highly appreciate: Find out what kind of arguments the recipe has and let the user input them. There are mandatory and optional arguments. There should be a description.

[AB-xdev]

A feature i would highly appreciate: Find out what kind of arguments the recipe has and let the user input them. There are mandatory and optional arguments. There should be a description.

👍 Note: Will likely require some kind of inspection (because there might be Java annotations)

I would completely kill the idea of "Writing recipes". That is a nightmare and we shouldn't be involved in that. The Using-Part is much more in demand IMHO.

Hmm not sure about this, Luis told me before that he would appreciate a kind of auto-completion (because always googling for it is not a good workflow). But yes I agree this is low prio.

[rfichtner]

Let's do the execution part first.

Once the plugin generates some traction, we can talk about writing recipes.

[AB-xdev]

UI design draft:

[AB-xdev]

Superseded by #5