@revenexx/studio-integrations 1.4.1 → 2.1.0

package/CHANGELOG.md

@@ -1,5 +1,302 @@
 # @revenexx/studio-integrations
 
+## 2.1.0
+
+### Minor Changes
+
+- 6ff6833: A workflow can be exported to a file and imported again, into the same environment or
+  another: Export as file in a workflow's row actions and in the editor's actions menu, Import
+  from file in the New workflow dialog, and Import from file… in the editor to replace a
+  workflow's content. The file never carries credentials, secret values or a webhook's
+  address; an import creates a paused workflow, or replaces the editor's content as
+  unsaved changes that keep each webhook's address and leave an active workflow running
+  until a valid version is saved (PO-525).
+- 9721bc2: PO-537: inside a palette folder, the nodes stand in the order their package gives
+  them rather than in the alphabetical order of their identifiers.
+
+  A node that states its place (`paletteOrder` in its manifest) comes first; the rest
+  follow in the order the package lists them, which the Integrations API now reports
+  as `package_position`; a node for which neither is known still falls back to its
+  identifier. So "Send Email" leads Brevo's Email folder instead of "Cancel Scheduled
+  Email".
+
+  Where a folder holds nodes of several packages, each package orders only its own:
+  no node takes a place another package's node held. Against an API that does not
+  report `package_position` yet, folders keep today's order.
+
+- 1820289: A run's record now shows what the run returned per step: one block for each step, under the name it carries on the canvas, in the order of the steps in the workflow — the way the dialog after a run already shows it. Before, the record printed the result as one object keyed by internal node ids, in an order the run never took. A result the workflow's steps cannot account for, because the workflow has changed since the run, say, is still shown whole.
+- 6cc8b71: A node's optional settings fold only after its last required setting. Before, every optional setting from the fourth on was folded wherever it stood, so a setting between two required ones vanished from the middle of the form, and one "Show n optional settings" control opened settings in two separate places. Everything up to the last required setting is now always shown, and the fold is one tail at the end — Brevo's Double Opt-in, for one, now shows "Never on lists" and folds only "Attributes".
+- 664725b: A mapped value in a node's setting can now be changed where it stands. Click it
+  to select it, then click it again or press Enter, and it opens as the expression
+  it stands for;
+  once the caret or the focus leaves it, it reads as its source again. Until now it
+  could only be deleted and written again, which for a condition meant retyping the
+  whole expression to correct one character (PO-544).
+- 7fd02ea: The node palette's folders now stand alphabetically on every level, in the
+  language the studio is shown in and regardless of case. Until now a folder stood
+  where its first node's internal identifier fell in the catalogue, so Test Nodes
+  appeared between PostBin and Shipcloud. SFTP is no longer pinned directly after
+  FTP; the nodes inside a folder keep the order their package gives them (PO-545).
+- 7525758: A Core folder in the node palette is one folder in every language (PO-546). The studio now names the Core folders it knows — Flow, Data, Text & Formats, Files, Web, Messaging, FTP / SFTP — from its own translations, by their English name, so a node that names no folder, or one an older release left registered with an out-of-date name, no longer opens a second folder (_Data_ beside _Daten_, _Flow_ beside _Ablauf_). Every one of them has its own icon. A path of two levels no longer files a node under Integrations — only an app package or a logo does — so Core can nest a folder; a subfolder without a logo shows the first image its nodes carry.
+
+### Patch Changes
+
+- ddcbdbd: The Schedules page says why a schedule will not fire, in the Next run column: its
+  workflow is inactive or not built, its schedule cannot be read, its timezone is
+  unknown, or its rhythm never comes round. Until now every one of these read as a
+  bare dash beside a live badge. A paused schedule and one with no schedule set keep
+  the dash, because the row already says so (PO-261).
+- ebbc148: Nothing a user sees changes. The module now declares `@solar-icons/vue`, which its
+  components already import through `@solar-icons/nuxt`. A host that typechecks and
+  sees every `#solar-icons` import reported as a missing export has to declare
+  `@solar-icons/vue` itself: the type declaration is generated into the host's own
+  `.nuxt`, so it is resolved from the host's dependencies, not this module's (PO-281).
+- fd5a78e: Nothing a user sees changes. The module is linted now, and the first run's fixes ship
+  in it: unused imports and dead helpers removed, the pattern that finds `${{ … }}` in a
+  setting no longer slows down on long unclosed input, and the OAuth popup renders one
+  root element (PO-305).
+- d9f4742: Cancelling a run from its row in either run list now asks first, the way terminating
+  already did and the way the run's record asks before both. A cancelled run cannot be
+  resumed, only retried from the start, so a slip in the row's menu was as final as a
+  terminate (PO-336).
+- 271de84: A run the platform reports as `canceled` — Temporal's spelling — or in another letter case (`COMPLETED`) now reads the same in the Runs list as at its own record. The list used to draw such a run as _failed_ while the record called it _cancelled_ or _succeeded_; both now read the platform's status through one table.
+- 90d9ae3: "How long ago" reads the same everywhere it is shown: the dashboard's Latest executions and
+  Needs attention panels, the runs list's Started column and a credential's last
+  check. Under ten seconds is "just now", from there to a minute it counts seconds
+  ("40s ago") — the dashboard used to say "just now" for the whole minute — and on
+  the dashboard and the runs list that count keeps moving between realtime events.
+  From thirty days on it is a date in the studio's language instead of a count like
+  "412d ago". A timestamp that cannot be read shows "—"; the dashboard used to print
+  "NaNd ago" (PO-393).
+- 60ef22a: The Shipcloud package's node icons draw as icons rather than as grey boxes.
+
+  A node declares its icon as an `mdi:` name and the studio renders Lucide, so the
+  two vocabularies are bridged by a table. A name in neither the table nor Lucide's
+  own spelling silently becomes a generic box — which is what the Shipcloud package
+  got for its nodes. Eight names now map: `truck-delivery`,
+  `package-variant-closed-plus`, `map-marker-path`, `package-variant-remove`,
+  `truck-check-outline`, `file-document-outline`, `file-plus-outline` and
+  `map-marker-radius-outline`.
+
+  The table also has a test now, including one that fails on an entry pointing at a
+  Lucide component that does not exist: a wrong entry looks exactly like a missing
+  one, and neither says anything.
+
+- 78e99d6: A number typed into a setting's mapped-value mode is kept as a number, not as text
+  (PO-521).
+
+  **A numeric setting has two boxes and only one of them kept the number.** The plain
+  one wrote what was typed as a number; the box beside it — the one that also takes a
+  value mapped from elsewhere in the workflow — wrote the raw text through. Brightness
+  50 was stored as `"50"`, the workflow saved without a word, and the run stopped with
+  `Config field 'brightness' must be of type number.` Nothing in that field could fix
+  it, because the field itself is what produced the text. Reported from the Philips Hue
+  **Set Light** node, where every value the author touched was text and the one they
+  left at its default was a number.
+
+  The rule now lives in one place: a numeric setting keeps the number, an emptied box
+  is no value rather than `''`, a mapped value is left exactly as it was typed, and
+  text denoting no number is kept as typed so the operator sees what they wrote rather
+  than finding the box silently emptied. Text in one of the three base notations —
+  `0x10`, `0b101`, `0o17` — counts as no number here, since the platform refuses it on
+  the way in and storing 16, 5 or 15 would put a value in the workflow nobody typed.
+
+  **When the conversion happens differs by box, and has to.** The plain one converts as
+  it is typed. The mapped-value box shows a document rather than a line of text, and it
+  re-projects that document whenever it disagrees with the value it is given — so it
+  stores what was typed and converts when it is left. Converting there on every
+  keystroke would rebuild the document under the operator's cursor: a number typed over
+  what the box already held would keep only its last digit, and `0.4` could never be
+  typed at all, because half-way through it is `0.` — a number worth `0`, whose text has
+  no dot in it. The range a
+  setting allows is read through the same rule, so a workflow **saved before this
+  change** — its number still stored as text — is marked in the dialog instead of
+  reading as sound until the run refuses it.
+
+  A yes/no setting has the same shape of defect and is deliberately untouched; it is
+  recorded in the Gaps of `specs/node-configuration.md`, with why.
+
+  The platform half of PO-521 ships separately: cross-validation now reads a numeric
+  setting's value as the number it denotes, which is what lets the workflows already
+  saved this way run again without anything rewriting them.
+
+- 2632bae: A credential type's logo sits in a smaller box: 8 px larger than the symbol instead of
+  16, so 24 px on the Credentials list instead of 32, with the type picker and the
+  credential dialogs shrinking in step. The generic key shown for a type without a logo
+  shrinks with it (PO-527).
+- 1159568: PO-542: nodes whose icon the studio could not translate no longer draw as an
+  empty box.
+
+  Node packages name their icons in one vocabulary and the studio draws another, so
+  each name goes through a table; a name missing from it fell back to the generic box
+  without a word. The table now covers the names the packages ship today — all of
+  Philips Hue and PostBin, sixteen Brevo nodes, the notifications nodes, and one each
+  in core and DeepL. The four chat brands (Discord, Microsoft Teams, Telegram,
+  WhatsApp) have no counterpart in the drawing set and get a neutral messaging
+  symbol; their vendor logo still marks them.
+
+## 2.0.0
+
+### Major Changes
+
+- 8397d7b: Every studio list is read as a table, its search box states its own name, and the Runs
+  filter works again on `@revenexx/studio-shared` 0.3.2 (PO-233).
+
+  **A row of any studio list used to be an unnamed sequence of values.** The shared table
+  rendered anonymous boxes, so nothing connected a column heading to the cell beneath it:
+  a schedule read as _"Order sync, Daily at 03:00, Europe/Berlin, in 18m, 1h ago, live"_,
+  with nothing saying which of the two times was the next run. Taking `studio-shared`
+  0.3.2 gives every list — Workflows, Runs, Schedules, Credentials, Secrets and the Audit
+  Log — `table`, `row`, `columnheader` and `cell`, so each value is announced under the
+  heading it belongs to. The search above each list now states its name on the field
+  itself, in the words of its own placeholder, instead of leaving the browser to work one
+  out from that placeholder — which is a fallback rather than a name, and a documented
+  failure pattern when it is the only one.
+
+  **Two cells on the Schedules page lost the labels they carried.** They were there so a
+  test could find them, and a name on a cell is read _instead of_ its contents — so with
+  the semantics in place they announced "Next run" where the time should be. The heading
+  above the column says which time it is now, which is what it is for.
+
+  **The Runs filter is rebuilt as two selects.** In 0.3.2 the shared filter trigger opens
+  a popover rather than a dropdown menu, and the sub-menus this page put inside it had no
+  menu to attach to: they rendered nothing at all, so the control was there and the
+  narrowing was gone. Outcome and trigger kind are now chosen from a select each, `All`
+  included, and the narrowing reaches the platform exactly as before.
+
+  **A host also owes the shared table two new catalogue entries.** `studio-shared`
+  translates through the host's own `shared.*` catalogue and renders the key itself when
+  an entry is missing, and 0.3.2 asks for `shared.datatable.toolbar.filter.apply` and
+  `…toolbar.filter.reset` — the two buttons of the filter panel, which a host without
+  them draws as the key names. The cockpit already carries both, in either language; any
+  other host has to add them. (`…toolbar.search.aria.label` is asked for too, but no list
+  in this module reaches it: the table names the search box after its own placeholder
+  unless a surface says otherwise, and all six pass a placeholder.)
+
+  **This is a major for two of the reasons [`docs/versioning.md`](docs/versioning.md)
+  names.** The peer floor on `@revenexx/studio` rises from `*` to `^0.2.3`, so a host on
+  the old range can no longer install — and four accessible names are removed rather than
+  renamed: `Next run`, `Last run`, `When it fires` and `Cron expression`, which anything
+  addressing a schedules cell by name was using. Both are things a host has to react to.
+
+  **Hosts must be on `@revenexx/studio` ^0.2.3.** The peer range was `*` and is now the
+  version that carries the search field's `label` prop; below it the name falls through to
+  a wrapper and the box stays anonymous.
+
+- c651aac: The editor no longer points out an error output nobody connected. The run says it instead
+  (PO-479).
+
+  **What goes.** A strip above the canvas read _"{n} node routes failures to an output with
+  nothing attached — nothing handles the failure there."_, named each step, and offered to
+  attach a **Stop and Error** step to the port in one click. The strip, that action, and the
+  five promises in `specs/workflow-advice.md` are withdrawn.
+
+  **Why, and what an author loses.** The strip and the platform behaviour it described
+  shipped together under PO-443. The platform half is the one that can speak with authority:
+  a failure routed to an output nothing leaves now **ends the run**, naming the step, what it
+  failed with, and which output had nowhere to send it — the `node-failure-handling` spec of
+  `revenexx/integrations`, AC-8. Before PO-443 such a failure vanished and the run was
+  recorded as a success, which is the world the strip was built for and which no longer
+  exists. What is genuinely lost is the timing: an author used to be told while drawing, and
+  is now told by the first run that actually fails.
+
+  **`revenexx:stop-and-error` is untouched.** It is still in the palette, still what all eight
+  shipped templates put behind each of their twenty-five error ports, and still the right
+  thing to attach. Only the editor's one-click attachment is gone.
+
+  **A major, for the reason [`docs/versioning.md`](docs/versioning.md) gives.** Seven strings
+  are removed rather than renamed, and three of them are accessible names or an action label
+  that a host or a test could be addressing:
+
+  | Removed                                    | What it was                                 |
+  | ------------------------------------------ | ------------------------------------------- |
+  | `integration.editor.errorPath.advice`      | the strip's own sentence                    |
+  | `integration.editor.errorPath.action.stop` | _Stop the run on error_                     |
+  | `integration.editor.errorPath.ariaReveal`  | accessible name of the step link            |
+  | `integration.editor.errorPath.ariaFix`     | accessible name of the attach action        |
+  | `integration.editor.errorPath.more`        | _…and {n} more_                             |
+  | `integration.editor.errorPath.message`     | the pre-filled message on the attached step |
+  | `integration.editor.errorPath.toast.added` | the toast after attaching                   |
+
+  Nothing else in the editor moves: the validation banner, the reauth strip and the build
+  notice keep their place above the canvas, and the activation gate is unchanged — the strip
+  never touched it, which was the whole point of it.
+
+### Patch Changes
+
+- a79380d: The dialog that imports a platform SFTP account can be drawn by any host built to the
+  written contract, and its wait is now a promise with a test behind it (PO-387).
+
+  **The studio's written contract for a host was five members behind what this dialog
+  reads.** `src/runtime/utils/cockpitSources.ts` says what the module expects of a cockpit
+  host, and its `sftp` entry declared neither `loading` nor `activeTenantSlug`, made
+  `load`'s tenant argument required where the cockpit makes it optional, and left `server`
+  and `home_directory` off an account. The dialog read all five. The cockpit has provided
+  all five throughout, so **nothing was ever wrong for an operator** — what was wrong is
+  that a host built to the contract instead of to the cockpit threw
+  `TypeError: Cannot read properties of undefined` while drawing the dialog. Vue's error
+  handler turns that into a console message and unmounts the tree, so the page went blank
+  with no error anything could catch.
+
+  **The consequence was that no test could reach the surface at all.** The playground's
+  stand-in for the cockpit is built from the contract, so switching it on crashed the
+  dialog and leaving it off gave a dialog that never waits — the only two states the suite
+  could produce. The waiting announcement PO-251 added here was therefore recorded as a
+  gap rather than a criterion. The contract and the stand-in now carry all five members,
+  the dialog takes its type from the contract rather than declaring its own, and
+  `specs/node-configuration.md` carries the wait as AC-33 with a test that fails when the
+  announcement is taken away.
+
+  **A failed fetch no longer reads as a tenant with no accounts.** The surrounding
+  application catches its own fetch errors, so the studio is handed an empty list and no
+  exception — and the dialog drew the same "No active platform SFTP accounts. Create one
+  under Integration Studio → SFTP first." for both. One of those two asks the operator to
+  go and create an account; the other does not, and nothing on screen let them tell which
+  they were looking at. The contract gains the `error` the cockpit has always exposed —
+  **optional**, because the standalone dev studio's stand-ins provide the other four
+  members and not that one, and a dialog that insisted on it would lose that host the
+  whole surface. Where it is absent the dialog keeps the empty state it showed before.
+  That is AC-34, and it adds one string in both languages: **"The platform SFTP accounts could not be loaded:
+  {message}"** / "Die Plattform-SFTP-Konten konnten nicht geladen werden: {message}".
+
+  **A patch.** `CockpitSftpAccount` gains two required members, which
+  [`docs/versioning.md`](docs/versioning.md) would put in the major column as a narrowed
+  type — but only for somebody who can reach it. Nobody can: `exports` in `package.json`
+  declares `"."` alone and no `typesVersions`, so every other subpath is sealed and
+  `require.resolve` of the file answers `ERR_PACKAGE_PATH_NOT_EXPORTED`. The type ships
+  inside the tarball and is importable from nowhere. The dialog reads exactly what it read
+  before, so a host that worked goes on working unchanged.
+
+- 8975a1f: The Credentials list offers the provider step to a credential that never took it, not
+  only to one whose authorisation expired (PO-478).
+
+  **A three-legged credential is created before its provider is asked.** The dialog closes
+  on the creation, and the window that asks for consent is opened after that — so when
+  that second step fails, there is no dialog left to say so. What remained was a
+  credential that cannot work, wearing the same _Not Connected_ badge as one nobody has
+  tested, with nothing in its row to finish what was started. The only way on was to
+  delete it and make it again.
+
+  **The row now offers the step wherever a three-legged credential is not known to be
+  connected**, and the wording says which of the two it is: **Connect** where nothing has
+  ever proved the credential connected, **Reconnect** where it was working and stopped —
+  an authorisation that expired, or a connection test that failed. The amber stays on the
+  expired one, which is the case this surface has always marked for attention. A
+  credential whose access data is a key, a host or a password never carries either, which
+  is what keeps the offer from becoming background noise.
+
+  It is generous by exactly one case: a credential that _was_ authorised but never tested
+  also carries the offer, because nothing the service returns tells that apart from one
+  that was never authorised. Taking the step again is the same window the operator was
+  expecting, so the cost of that guess is a click.
+
+  Promised behaviour: `specs/credentials.md` AC-2. The `## Gaps` entry in
+  `specs/credential-create.md` that asked what this surface says when the step after the
+  close fails is answered, and now points here.
+
+- c787791: No product change: a spec's `## Gaps` entry and a test comment now say only what was
+  measured about `canvas-navigation` AC-4 (PO-479).
+
 ## 1.4.1
 
 ### Patch Changes

package/README.md

@@ -74,7 +74,7 @@ component styling silently breaks:
 Adjust the relative paths to reach `node_modules` from your CSS file.
 
 ## Peers
-`@revenexx/studio`, `@revenexx/studio-shared` ^0.2 (module form), `nuxt` ^4, `vue` ^3.5,
+`@revenexx/studio` ^0.2.3, `@revenexx/studio-shared` ^0.3.2 (module form), `nuxt` ^4, `vue` ^3.5,
 `@vue-flow/*` + `@dagrejs/dagre` (workflow editor), `lucide-vue-next`; register
 `@solar-icons/nuxt` in the host.
 
@@ -86,6 +86,7 @@ cockpit monorepo under `packages/studio-integrations`).
 ```bash
 pnpm install     # runs the module `prepare` (nuxt-module-build)
 pnpm test        # vitest
+pnpm lint        # eslint — `pnpm lint --fix` fixes what has a fix, layout above all
 pnpm build       # dist/
 pnpm changeset   # record what your change does to the version
 ```

package/dist/module.json

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

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

@@ -149,16 +149,16 @@ async function submit() {
           {{ t("integration.credentials.createDialog.noTypeAvailable") }}
         </p>
         <button
-          v-for="t in allowedTypes"
-          :key="t.slug"
+          v-for="type in allowedTypes"
+          :key="type.slug"
           type="button"
           class="flex w-full items-center gap-2 rounded-lg border border-black/[0.08] p-3 text-left transition hover:border-black/20 hover:bg-muted/30"
-          @click="pickType(t)"
+          @click="pickType(type)"
         >
-          <IntegrationsCredentialLogo :type="t" :size="18" />
+          <IntegrationsCredentialLogo :type="type" :size="18" />
           <div class="min-w-0 truncate text-sm">
-            <span class="font-semibold">{{ resolveLocalized(t.name) }}</span>
-            <span class="ml-1.5 text-muted-foreground">({{ authKindLabel(t.auth_kind) }})</span>
+            <span class="font-semibold">{{ resolveLocalized(type.name) }}</span>
+            <span class="ml-1.5 text-muted-foreground">({{ authKindLabel(type.auth_kind) }})</span>
           </div>
         </button>
       </div>