Allow deleting steps using the keyboard

[BrunoOrchest]

Description

When user selects a step, the Title field is no longer auto focused to allow the delete/backspace keys to delete the step. In the case the step was just added, the Title field is focused so the user can start writing normally

Fixes: #556

Checklist

• The documentation reflects the changes.
• The PR branch is set up to merge into dev instead of master.
• In case I changed one of the services’ models.py I have performed the appropriate database
  migrations (refer to scripts/migration_manager.sh).
• In case I changed code in the orchest-sdk I followed its release
  checklist
• In case I changed code in the orchest-cli I followed its release
  checklist
• I haven't introduced breaking changes that would disrupt existing jobs, i.e. backwards
  compatibility is maintained.
• In case I changed the dependencies in any requirements.in I have run pip-compile to update
  the corresponding requirements.txt.

[yannickperrenet]

Works like a charm! 👍

I quite like this behavior, feels "natural".

[iannbing]

Currently it seems that we have to carefully set the value of shouldAutoFocus back to false case by case. Is there a simpler way, for example, always reset shouldAutoFocus to false for all actions except forCREATE_STEP or DUPLICATE_STEPS?

[BrunoOrchest]

Currently it seems that we have to carefully set the value of shouldAutoFocus back to false case by case. Is there a simpler way, for example, always reset shouldAutoFocus to false for all actions except forCREATE_STEP or DUPLICATE_STEPS?

Not necessary since the SELECT_STEPS and related will take care of that. Other actions don't trigger the properties visibility so no need to be 'spamming' the code all over since the selection/deselection will take care of it always.

[iannbing]

@BrunoOrchest You could set shouldAutoFocus as false before the switch instead of "spamming" in each case.

const state  = { ...currentState, shouldAutoFocus: false };

switch (action.type) {

     case "CREATE_STEP": {
          return {
                ...
                shouldAutoFocus: true,
           }
     } 

     // No need to set shouldAutoFocus to false in any other case.
}

The current implementation could lead to missing cases. For example:

• there's an existing step A
• create a new step
• Immediately select step A: the title field is auto-focused. (because in case SET_OPENED_STEP, shouldAutoFocus is not set to false. Was it intended?).