Provide default/primary action on "Run"
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
- Users: "This workflow is beautiful! How do I run it?"
- OpenFn: "Yeah no worries... click the
▷ Runbutton, then pick what input to use with the run you're about to create (we'll default that to a sensible option but still want you to verify) and then when you're happy with the input dataclip, click the other▶ Runbutton. Note that the second time you have to click▶ Runthe little triangle "play" icon is filled in. This is the international standard for 'no no this time it will actually run trust me.' Understood? - Users: 😵💫
Ok... so flexibility is WONDERFUL, but we should consider removing a step here if 80% of users want to run with the default input 80% of the time.
What we know:
Right now we have two types of "Run" buttons:
- The
▷ Runbutton in the top menu opens the "create new run with 1 of 3 inputs" panel/dialog. - The
▶ Runbutton actually executes a run with the chose input (which defaults toemptyfor webhook triggered workflows, tonext_cron_statefor cron-triggered workflows, andcurrent_step.input_dataclipwhen a step/run is loaded.)
Feedback we've gathered:
- It's confusing to see a button called "Run" which doesn't actually run.
- Most users want to run with the default input anyway.
- Users who want to run with a custom input or existing input are advanced users with more knowledge of the app and are cool using a split-button/alt-button.
Proposed solution:
When you click the run, button... it runs.
(And if you want the alternate, you click the dropdown.)
- Use the split button
- Make the primary action (
cmd-enter) a shortcut to "actually create new run with default input" - Make the second action (
cmd-shift-enter) a shortcut to "open the 'create new run with 1 of 3 inputs' panel/dialog".
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing top-menu Run button, the create-new-run input panel, and the current cmd-enter and cmd-shift-enter shortcuts. Confirm how each workflow trigger selects its default input. Done means the primary split-button action runs with that default, while the alternate action opens the input-selection panel and both shortcuts match the proposed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100