In the inspector, when I'm editing my job code, I can't run my job unless I have some input.
Well, okay, fair enough, but I also find myself setting {} to my input all the time. I’d love it if I could just run the job and, if I haven’t specified an input, for {} to be used.

Possible that this touches on #2944 - a bug we've discovered recently.

Note that this is not the big request for manual runs, but rather a short-term, high-value improvement to quality of life.

Here's more information from @taylordowns2000 :

A really big bug-bear for the group (in Ghana) this week was having to type {} in the left side panel to run a job. This was probably the biggest common blocker to the UX.

I’m quite eager to introduce the “better manual runs” stuff (with those diagrams I’ve shared already) diagrams

But in the meantime, I was expecting that this would work:

@@ -123,6 +123,7 @@ defmodule LightningWeb.WorkflowLive.ManualWorkorder do
     <div :if={is_nil(@selected_dataclip)} class="grow">
       <.input
         type="textarea"
         value="{}" # 👈 Look here!
         field={@form[:body]}
         disabled={@disabled}
         class="h-full font-mono proportional-nums text-slate-200 bg-slate-700"

That one line addition sets the default value to {} which I think is great… if you don’t specify an input and just want to run get('https://www.google.com/') we let you type that and then hit run. End of story!

But… it doesn’t actually work. The run button is greyed out. Ayo thinks it may be related to the run button listening to an onchange event in the input panel. If I click into the input after this default value loads, backspace to remove a } and then type the same { back, everything is perfect.