Closed AB-xdev closed 5 months ago
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.
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.
Let's do the execution part first.
Once the plugin generates some traction, we can talk about writing recipes.
UI design draft:
Superseded by #5
ℹ️ = Non primary goal idea
Executing recipes
above