Execute Script V2 - UX

[deanhannigan]

Description

UX updates to accomodate the new version of the JavaScript automation type.

• Added the UX for the new JavaScript step type (EXECUTE_SCRIPT2)
  • The code editor is now displayed directly in the step, making the code immediately visible and allowing quicker edits.
  • The editor provides the same the core builder binding UX with suggestions and snippets.
• CodeEditorField - extracted the CodeEditor UX from deep with the BindingPanel so that it can be used as a standalone UX. Supports JS only for the moment
  • A precursor to future binding fields improvements. The field would ideally house all binding UX behaviours and replace the CodeEditor in the BindingPanel entirely. That is beyond the scope of this ticket.
• Update Row binding UX switched back from modal to drawer mode to keep it in line with the other steps.
• Added an automation evaluation context containing; Trigger, User, Step and Settings data. When selecting a suggestion in the dropdown, it will display any available data in the UI!
• Legacy JavaScript (EXECUTE_SCRIPT) step has been deprecated. Any automations still using the legacy step will function as before and no action is required.

Fixes

• Fix - Binding icons in Attachment|Signature drawers were all defaulted to ShareAndroid. They reflect the correct category now.
• Fix - Timing issue with the Bindable drawer across the builder.
  • When the text value was updated, other elements in the drawer would update but CodeEditor would get stuck with the initiating value. This caused a timing issue for all bindable inputs if they had an "update on blur" UX.
• Fix - Added support for using spaces when configuring fields for App Action triggers. This has been an annoyance for a while.
  • My field encodes as trigger.fields.[My field] and is displayed as trigger.fields.My field.
• Fix - Blurring a field name input in an App Action step, without altering it, would trigger an empty update and throw an error
• Fix - Webhooks that have no test data would throw errors when modifying.
• Fix - Minor adjustment to the App Action trigger field UX adding a little flexibility when configuring
  • Empty/unused fields will still be cleared after a successful save
• Fix - Added table parameter to the Row action in the test endpoint as it was missing from the test results.
• Fix - Automation icons panel was displaying the incorrect icons. The list would display the icon associated with the first automation in the group. Now they reflect their corresponding automation definition types
• Fix - Row types mislabelled as 'Multi select' in the bindings drawer.

Addresses

• https://linear.app/budibase/issue/BUDI-9024/automation-javascript-step-v2-ux
• https://linear.app/budibase/issue/BUDI-7129/trigger-row-automation-handlebars-do-not-support-column-names-with
• Automation Trigger fields will delete themselves if the user clicks to change type with no name set #15168

Screenshots

JavaScript V2 UX. The code is directly visible and editable in the step, with suggestions and snippets . Suggestions will also render/evaluate any data in your test results or some default data

Live binding evaluation in all fields!

Launchcontrol

Automation Execute Script V2 and general Automation fixes

Feature branch env

Feature Branch Link

[qa-wolf]

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!