@revenexx/studio-integrations 1.1.1 → 1.3.0

package/dist/runtime/utils/stateNamespaceName.d.ts

@@ -0,0 +1,23 @@
+/**
+ * The engine's grammar for a state namespace (PO-374), mirrored in the browser
+ * so a name it would refuse is rejected while the author types rather than as a
+ * 422 about `blob.state.0` on save.
+ *
+ * One copy on purpose. Two surfaces declare namespaces — the workflow's State
+ * dialog and the picker inside a node's state setting — and a grammar spelled
+ * once per surface is one that widens or narrows in a single place, leaving the
+ * other accepting names the engine has stopped taking.
+ */
+export declare const STATE_NAMESPACE_PATTERN: RegExp;
+/**
+ * Which message a typed namespace name earns, as a translation key — or `null`
+ * when there is nothing to say. Both callers show the same sentence for the same
+ * mistake, which is the other half of holding the grammar in one place.
+ *
+ * An empty field returns `null`: nobody has answered yet, and a rejection shown
+ * before the first keystroke reads as a rejection of the dialog.
+ *
+ * @param name  what the author has typed, trimmed here rather than by the caller
+ * @param taken the names the workflow already declares
+ */
+export declare function stateNamespaceErrorKey(name: string, taken: string[]): string | null;

package/dist/runtime/utils/stateNamespaceName.js

@@ -0,0 +1,8 @@
+export const STATE_NAMESPACE_PATTERN = /^[a-z][a-z0-9]*([._-][a-z0-9]+)*$/;
+export function stateNamespaceErrorKey(name, taken) {
+  const value = name.trim();
+  if (!value) return null;
+  if (!STATE_NAMESPACE_PATTERN.test(value)) return "integration.workflows.state.error.invalidName";
+  if (taken.includes(value)) return "integration.workflows.state.error.nameExists";
+  return null;
+}

package/dist/runtime/utils/validationFindings.d.ts

@@ -38,8 +38,10 @@ export interface FindingNodeGroup {
     /** The node's human label; `null` when `nodeId` is. */
     label: string | null;
     /**
-     * One compact entry per finding, in order and de-duplicated: the config key
-     * the path ends in, falling back to the message when the path carries none.
+     * One compact entry per finding, in order and de-duplicated by config key: the
+     * setting's name as `fieldLabelOf` gives it — the manifest's label for the banner,
+     * the bare key where a caller asks for that — falling back to the message when the
+     * path carries no config key at all.
      * **Empty when `nodeId` is `null`** — read `messages` instead.
      */
     fields: string[];
@@ -53,6 +55,27 @@ export interface FindingNodeGroup {
  * two of them prints `revenexx:business-central-create-customer` at the user.
  */
 export declare function nodeDisplayLabel(node: WorkflowNode): string;
+/**
+ * What a setting is called, for somebody reading *about* it.
+ *
+ * The same lookup {@link nodeDisplayLabel} does for the node, one level down: the
+ * manifest carries a bilingual `label` per config field, and the node's own settings
+ * form already renders it. The banner did not ask, so it printed the blob path's last
+ * segment — `companyId` beside a form that says **Firma**, in an otherwise German
+ * screen, for the same field (PO-401).
+ *
+ * **The key is the fallback and never the wrong answer.** A workflow can outlive the
+ * manifest version it was saved against, and a package can be gone entirely; then there
+ * is no label to resolve, and the raw key is worse to read but still names the setting
+ * the operator has to find. Falling back to the finding's *message* — what this module
+ * does for a finding with no field key at all — was refused here: it turns a short list
+ * of names into a list of sentences exactly when the banner is already hardest to read.
+ *
+ * **For reading about, not for finding by.** `findingsByNodeField` deliberately does NOT
+ * use this. Its keys are how the configuration dialog attaches a message to an input, so
+ * a translated one would stop matching the field it belongs to.
+ */
+export declare function fieldDisplayLabel(node: WorkflowNode, fieldKey: string): string;
 /**
  * The setting a finding is about: the config key its path ends in.
  *
@@ -71,7 +94,7 @@ export declare function findingFieldKey(path: string): string | null;
  * `null` nodeId), rendered after the node groups — it has no node to hide
  * behind, and dropping it would lose an issue the user has to fix.
  */
-export declare function groupFindingsByNode(findings: readonly ValidationFinding[], nodes: readonly WorkflowNode[], labelOf?: (node: WorkflowNode) => string): FindingNodeGroup[];
+export declare function groupFindingsByNode(findings: readonly ValidationFinding[], nodes: readonly WorkflowNode[], labelOf?: (node: WorkflowNode) => string, fieldLabelOf?: (node: WorkflowNode, fieldKey: string) => string): FindingNodeGroup[];
 /**
  * Node id → config key → the message to show AT that setting
  * (specs/node-configuration.md AC-8).

package/dist/runtime/utils/validationFindings.js

@@ -5,6 +5,11 @@ export function nodeDisplayLabel(node) {
   const manifest = findManifest(node.nodeSlug, node.nodeVersion);
   return resolveLocalized(node.name) || resolveLocalized(manifest?.name) || node.nodeSlug;
 }
+export function fieldDisplayLabel(node, fieldKey) {
+  const manifest = findManifest(node.nodeSlug, node.nodeVersion);
+  const field = manifest?.config?.find((f) => f.key === fieldKey);
+  return resolveLocalized(field?.label) || fieldKey;
+}
 export function findingFieldKey(path) {
   const m = /^blob\.nodes\.\d+\.config\.([^.[]+)/.exec(path);
   return m ? m[1] : null;
@@ -13,10 +18,11 @@ function findingNode(path, nodes) {
   const m = /^blob\.nodes\.(\d+)\b/.exec(path);
   return m ? nodes[Number(m[1])] : void 0;
 }
-export function groupFindingsByNode(findings, nodes, labelOf = nodeDisplayLabel) {
+export function groupFindingsByNode(findings, nodes, labelOf = nodeDisplayLabel, fieldLabelOf = fieldDisplayLabel) {
   const nodeGroups = [];
   const orphans = [];
   const byNodeId = /* @__PURE__ */ new Map();
+  const seenKeys = /* @__PURE__ */ new Map();
   for (const finding of findings) {
     const node = findingNode(finding.path, nodes);
     if (!node) {
@@ -29,8 +35,17 @@ export function groupFindingsByNode(findings, nodes, labelOf = nodeDisplayLabel)
       byNodeId.set(node.id, group);
       nodeGroups.push(group);
     }
-    const field = findingFieldKey(finding.path) ?? finding.message;
-    if (!group.fields.includes(field)) group.fields.push(field);
+    const key = findingFieldKey(finding.path);
+    if (key === null) {
+      if (!group.fields.includes(finding.message)) group.fields.push(finding.message);
+    } else {
+      const seen = seenKeys.get(node.id) ?? /* @__PURE__ */ new Set();
+      seenKeys.set(node.id, seen);
+      if (!seen.has(key)) {
+        seen.add(key);
+        group.fields.push(fieldLabelOf(node, key));
+      }
+    }
     group.messages.push(finding.message);
   }
   return [...nodeGroups, ...orphans];

package/package.json

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