@revenexx/studio-integrations 2.3.0 → 2.4.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @revenexx/studio-integrations
 
+## 2.4.0
+
+### Minor Changes
+
+- 22eb158: Run in the workflow editor no longer starts the saved version while the canvas shows unsaved changes (PO-567). A changed setting used to be run as its old value, with nothing on screen to say so. Run now stands in the header beside Save rather than in the canvas's control pane, and while there is unsaved work it reads **Save & run** (German **Speichern & Run**): the press saves first and runs the workflow as it then stands. A save that is refused, or waits on the question whether to keep the work as paused, starts no run. The canvas's right-click menu names the save the same way. The header's dispatch badge now shows the mode as entered in the settings, as the name beside it already did, because that is the mode the next run goes out in. `WorkflowEditor` loses its `runWaiting` prop and gains `runSaves`.
+
 ## 2.3.0
 
 ### Minor Changes

package/dist/module.json

@@ -1,7 +1,7 @@
 {
   "name": "@revenexx/studio-integrations",
   "configKey": "studioIntegrations",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "builder": {
     "@nuxt/module-builder": "1.0.2",
     "unbuild": "unknown"

package/dist/runtime/components/Integrations/WorkflowContextMenu.d.vue.ts

@@ -11,6 +11,8 @@ type __VLS_Props = {
     targetIsTrigger?: boolean;
     /** Busy flag for the Run item. */
     runBusy?: boolean;
+    /** The workflow has unsaved work, so the Run item saves it first — and says so. */
+    runSaves?: boolean;
 };
 declare var __VLS_14: {};
 type __VLS_Slots = {} & {

package/dist/runtime/components/Integrations/WorkflowContextMenu.vue

@@ -16,7 +16,8 @@ const props = defineProps({
   selectionCount: { type: Number, required: true },
   totalNodes: { type: Number, required: true },
   targetIsTrigger: { type: Boolean, required: false },
-  runBusy: { type: Boolean, required: false }
+  runBusy: { type: Boolean, required: false },
+  runSaves: { type: Boolean, required: false }
 });
 const emit = defineEmits(["action", "update:open"]);
 const t = useIntegrationsT();
@@ -33,7 +34,7 @@ const sections = computed(() => {
         { id: "duplicate", label: t("integration.canvas.contextMenu.item.duplicate"), shortcut: primaryShortcut("duplicate"), disabled: props.targetIsTrigger }
       ],
       [
-        { id: "run", label: t("integration.canvas.contextMenu.item.runWorkflow"), shortcut: primaryShortcut("run"), disabled: props.runBusy },
+        { id: "run", label: t(props.runSaves ? "integration.canvas.contextMenu.item.saveAndRunWorkflow" : "integration.canvas.contextMenu.item.runWorkflow"), shortcut: primaryShortcut("run"), disabled: props.runBusy },
         { id: "tidy-up", label: t("integration.canvas.contextMenu.item.tidyUp"), shortcut: primaryShortcut("tidyUp") }
       ],
       [

package/dist/runtime/components/Integrations/WorkflowContextMenu.vue.d.ts

@@ -11,6 +11,8 @@ type __VLS_Props = {
     targetIsTrigger?: boolean;
     /** Busy flag for the Run item. */
     runBusy?: boolean;
+    /** The workflow has unsaved work, so the Run item saves it first — and says so. */
+    runSaves?: boolean;
 };
 declare var __VLS_14: {};
 type __VLS_Slots = {} & {

package/dist/runtime/components/Integrations/WorkflowEditor.d.vue.ts

@@ -20,10 +20,13 @@ type __VLS_Props = {
      * keystrokes.
      */
     draft?: WorkflowBlob | null;
-    /** Busy flag for the control-pane Play button (a run is being triggered). */
+    /** A run is being triggered — the context menu's Run item and the shortcut stand down. */
     runBusy?: boolean;
-    /** The run is queued behind a bundle build — busy, but worth saying why. */
-    runWaiting?: boolean;
+    /**
+     * The workflow has unsaved work, so Run saves it first. Only the context menu
+     * reads it, to say so: Run itself stands in the page header, beside Save.
+     */
+    runSaves?: boolean;
     /**
      * One of the page's own lightboxes is open above the editor (settings,
      * duplicate, run payload, the sync response, the deactivation prompt). The

package/dist/runtime/components/Integrations/WorkflowEditor.vue

@@ -13,10 +13,8 @@ import { MiniMap } from "@vue-flow/minimap";
 import {
   Widget as LayoutGrid,
   MagicStick as Sparkles,
-  Play,
   MinusCircle as ZoomOut,
-  AddCircle as ZoomIn,
-  RefreshCircle as Loader2
+  AddCircle as ZoomIn
 } from "#solar-icons";
 import {
   Dialog,
@@ -65,7 +63,7 @@ const props = defineProps({
   workflow: { type: Object, required: true },
   draft: { type: [Object, null], required: false },
   runBusy: { type: Boolean, required: false },
-  runWaiting: { type: Boolean, required: false },
+  runSaves: { type: Boolean, required: false },
   overlayOpen: { type: Boolean, required: false }
 });
 const emit = defineEmits(["change", "run", "toggleActive", "openSettings"]);
@@ -1420,6 +1418,7 @@ const edgeTypes = {
         :total-nodes="vfNodes.length"
         :target-is-trigger="!!menu.targetId && blob.triggers.some((t2) => t2.id === menu.targetId)"
         :run-busy="runBusy"
+        :run-saves="runSaves"
         @action="onMenuAction"
       >
         <!-- `pan-activation-key-code` is null rather than left at its default, which
@@ -1695,25 +1694,6 @@ const edgeTypes = {
         <TooltipProvider :delay-duration="250">
           <div class="rounded-lg border border-gray-400/10 outline-1 outline-white/30 backdrop-blur-sm">
             <div class="flex items-center gap-0.5 whitespace-nowrap border border-white bg-white rounded-lg bg-gradient-to-br from-white via-violet-50/40 to-white px-2 py-1">
-              <!-- Smart Run: the page decides what "run" means — a workflow that
-               consumes trigger.payload, or leaves the mode to the caller, opens
-               the run dialog; one that asks neither fires immediately. One
-               button either way. -->
-              <IntegrationsEditorTip :label="runWaiting ? t('integration.editor.tool.run.tooltipWaiting') : t('integration.editor.tool.run.tooltip')" :shortcut="primaryShortcut('run')">
-                <button
-                  type="button"
-                  class="relative flex h-8 items-center gap-1.5 rounded-lg bg-gradient-to-b from-emerald-500 to-emerald-600 px-3.5 text-sm font-medium text-white transition after:pointer-events-none after:absolute after:inset-0 after:rounded-[inherit] after:shadow-[inset_0_1px_0_rgba(255,255,255,0.3),inset_0_-2px_0_rgba(0,0,0,0.25)] hover:from-emerald-600 hover:to-emerald-600 active:translate-y-px disabled:opacity-60"
-                  :disabled="runBusy"
-                  @click="emit('run')"
-                >
-                  <Loader2 v-if="runBusy" :size="14" class="animate-spin" />
-                  <Play v-else :size="14" />
-                  {{ runWaiting ? t("integration.editor.run.waitingForBuild") : t("integration.editor.run.button") }}
-                </button>
-              </IntegrationsEditorTip>
-
-              <div class="mx-1 h-5 w-px bg-black/10" />
-
               <div class="flex items-center gap-0.5 rounded-lg bg-black/[0.05] p-0.5 shadow-[inset_0_1px_2px_rgba(15,23,42,0.12)]">
                 <!-- Icon-only, and the tooltip is not an accessible name: each one
                says what it does itself, and whether it is the active mode. -->

package/dist/runtime/components/Integrations/WorkflowEditor.vue.d.ts

@@ -20,10 +20,13 @@ type __VLS_Props = {
      * keystrokes.
      */
     draft?: WorkflowBlob | null;
-    /** Busy flag for the control-pane Play button (a run is being triggered). */
+    /** A run is being triggered — the context menu's Run item and the shortcut stand down. */
     runBusy?: boolean;
-    /** The run is queued behind a bundle build — busy, but worth saying why. */
-    runWaiting?: boolean;
+    /**
+     * The workflow has unsaved work, so Run saves it first. Only the context menu
+     * reads it, to say so: Run itself stands in the page header, beside Save.
+     */
+    runSaves?: boolean;
     /**
      * One of the page's own lightboxes is open above the editor (settings,
      * duplicate, run payload, the sync response, the deactivation prompt). The

package/dist/runtime/i18n/messages/de.json

@@ -53,6 +53,7 @@
   "integration.canvas.contextMenu.item.paste": "Einfügen",
   "integration.canvas.contextMenu.item.rename": "Umbenennen",
   "integration.canvas.contextMenu.item.runWorkflow": "Workflow ausführen",
+  "integration.canvas.contextMenu.item.saveAndRunWorkflow": "Speichern & Workflow ausführen",
   "integration.canvas.contextMenu.item.selectAll": "Alle auswählen",
   "integration.canvas.contextMenu.item.tidyUp": "Aufräumen",
   "integration.canvas.edge.action.delete": "Verbindung löschen",
@@ -439,6 +440,7 @@
   "integration.editor.run.error.syncFailed": "Synchroner Run fehlgeschlagen",
   "integration.editor.run.error.syncTimeout": "Synchroner Run: Zeitüberschreitung",
   "integration.editor.run.loading": "Run wird geladen…",
+  "integration.editor.run.saveAndRun": "Speichern & Run",
   "integration.editor.run.waitingForBuild": "Warten auf Build…",
   "integration.editor.runPayload.action.latestEvent": "Letztes reales Event",
   "integration.editor.runPayload.action.latestEvent.title": "Letztes empfangenes Event dieses Topics einfügen",

package/dist/runtime/i18n/messages/en.json

@@ -53,6 +53,7 @@
   "integration.canvas.contextMenu.item.paste": "Paste",
   "integration.canvas.contextMenu.item.rename": "Rename",
   "integration.canvas.contextMenu.item.runWorkflow": "Run workflow",
+  "integration.canvas.contextMenu.item.saveAndRunWorkflow": "Save & run workflow",
   "integration.canvas.contextMenu.item.selectAll": "Select all",
   "integration.canvas.contextMenu.item.tidyUp": "Tidy up",
   "integration.canvas.edge.action.delete": "Delete this connection",
@@ -439,6 +440,7 @@
   "integration.editor.run.error.syncFailed": "Sync run failed",
   "integration.editor.run.error.syncTimeout": "Sync run timed out",
   "integration.editor.run.loading": "Loading run…",
+  "integration.editor.run.saveAndRun": "Save & run",
   "integration.editor.run.waitingForBuild": "Waiting for build…",
   "integration.editor.runPayload.action.latestEvent": "Latest real event",
   "integration.editor.runPayload.action.latestEvent.title": "Insert the latest received event of this topic",

package/dist/runtime/pages/integrations/workflows/[id].vue

@@ -400,7 +400,11 @@ async function run(mode) {
 }
 const payloadDriven = computed(() => payloadFieldsFromBlob(shownBlob.value ?? { nodes: [] }).length > 0);
 async function runFromEditor() {
-  if (!workflow.value) return;
+  if (!workflow.value || saving.value) return;
+  if (isDirty.value) {
+    await save();
+    if (isDirty.value) return;
+  }
   if (payloadDriven.value || workflow.value.execution_mode === "caller_decides") {
     runPayloadOpen.value = true;
     return;
@@ -817,14 +821,12 @@ async function confirmDeactivate() {
                   <WorkflowIconView :icon="shownIcon" :size="16" />
                 </span>
                 <span class="truncate" :title="shownName">{{ shownName }}</span>
-                <!-- The SAVED mode, beside a drafted name, and the difference is not an
-                   oversight. A name changes nothing about what happens when Run is
-                   pressed, so the header may show what the operator just entered. The
-                   dispatch mode decides what a run does — and a run goes to the
-                   workflow the platform holds, not to the draft. A badge following the
-                   draft would read SYNC over a button that fires an async run. -->
-                <Badge variant="outline" class="ml-1.5 shrink-0 border text-xs font-medium uppercase text-muted-foreground" :title="t('integration.editor.header.executionMode.title', { mode: modeLabel(workflow.execution_mode) })">
-                  {{ modeLabel(workflow.execution_mode) }}
+                <!-- The DRAFTED mode, like the name beside it: Run over a draft saves
+                   it first (PO-567), so this is the mode the next run goes out in. The
+                   saved one would read ASYNC over a button about to fire a sync run;
+                   the unsaved marker says the platform does not have it yet. -->
+                <Badge variant="outline" class="ml-1.5 shrink-0 border text-xs font-medium uppercase text-muted-foreground" :title="t('integration.editor.header.executionMode.title', { mode: modeLabel(draftedMode) })">
+                  {{ modeLabel(draftedMode) }}
                 </Badge>
               </template>
             </span>
@@ -927,8 +929,23 @@ async function confirmDeactivate() {
                 <Save v-else :size="12" />
                 {{ saving ? t("integration.editor.action.save.saving") : t("integration.editor.action.save.label") }}
               </Button>
+              <!-- Run stands beside Save because a run goes to the workflow the
+                 platform holds, not to the draft on the canvas: with the two at
+                 opposite ends of the screen, a changed value was run as the old one
+                 and nothing said so. While there is a draft the press saves it first,
+                 and the name says that it will (PO-567). -->
+              <Button
+                class="h-7 bg-emerald-600 text-sm text-white hover:bg-emerald-700"
+                :disabled="saving || running || syncLoading || waitingForBuild"
+                :title="waitingForBuild ? t('integration.editor.tool.run.tooltipWaiting') : t('integration.editor.tool.run.tooltip')"
+                @click="runFromEditor"
+              >
+                <Loader2 v-if="running || syncLoading || waitingForBuild" :size="12" class="animate-spin" />
+                <Play v-else :size="12" />
+                {{ waitingForBuild ? t("integration.editor.run.waitingForBuild") : isDirty ? t("integration.editor.run.saveAndRun") : t("integration.editor.run.button") }}
+              </Button>
               <!-- Activation is a standing state, not a transport control. The play
-                 symbol belongs to Run, 600 px away in the canvas's control pane,
+                 symbol belongs to Run, the button just before this one,
                  where pressing it makes one thing happen now; arming a workflow's
                  triggers looks like nothing happening at all. So this states the
                  state in the words the workflows list uses — Active, Paused — and
@@ -1064,8 +1081,8 @@ async function confirmDeactivate() {
             ref="editorRef"
             :workflow="workflow"
             :draft="draft?.blob ?? null"
-            :run-busy="running || syncLoading || waitingForBuild"
-            :run-waiting="waitingForBuild"
+            :run-busy="saving || running || syncLoading || waitingForBuild"
+            :run-saves="isDirty"
             :overlay-open="settingsOpen || duplicateOpen || importOpen || !!exporter?.open || deleteOpen || syncOpen || runPayloadOpen || deactivationOpen || leaveOpen"
             @change="onChange"
             @run="runFromEditor"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@revenexx/studio-integrations",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "type": "module",
   "description": "Integration Studio (core: workflows, node editor, runs, schedules, credentials, secrets, audit) as a standalone, publishable Nuxt module.",
   "repository": {