From 9e4cc32b78b52a3dbcd7ace74c2a2ab3eec9c40c Mon Sep 17 00:00:00 2001 From: Cornelius Suermann Date: Wed, 30 Apr 2025 16:28:52 +0200 Subject: [PATCH] fix: Use correct reference to 'test step' button (no-changelog) (#15018) --- packages/frontend/editor-ui/src/plugins/i18n/locales/en.json | 4 ++-- .../nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts | 4 ++-- .../nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts | 4 ++-- .../nodes/LocalFileTrigger/LocalFileTrigger.node.ts | 4 ++-- packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts | 4 ++-- packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts | 4 ++-- packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts | 4 ++-- packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts | 4 ++-- 8 files changed, 16 insertions(+), 16 deletions(-) diff --git a/packages/frontend/editor-ui/src/plugins/i18n/locales/en.json b/packages/frontend/editor-ui/src/plugins/i18n/locales/en.json index 43ace13f5b..3a4919667d 100644 --- a/packages/frontend/editor-ui/src/plugins/i18n/locales/en.json +++ b/packages/frontend/editor-ui/src/plugins/i18n/locales/en.json @@ -2272,8 +2272,8 @@ "nodeIssues.input.missing": "No node connected to required input \"{inputName}\"", "ndv.trigger.moreInfo": "More info", "ndv.trigger.copiedTestUrl": "Test URL copied to clipboard", - "ndv.trigger.webhookBasedNode.executionsHelp.inactive": "While building your workflow, click the 'listen' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time there's a matching event in {service}, the workflow will execute. These executions will show up in the executions list, but not in the editor.", - "ndv.trigger.webhookBasedNode.executionsHelp.active": "While building your workflow, click the 'listen' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time there’s a matching event in {service}, this node will trigger an execution. These executions will show up in the executions list, but not in the editor. ", + "ndv.trigger.webhookBasedNode.executionsHelp.inactive": "While building your workflow, click the 'test step' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time there's a matching event in {service}, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "ndv.trigger.webhookBasedNode.executionsHelp.active": "While building your workflow, click the 'test step' button, then go to {service} and make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time there’s a matching event in {service}, this node will trigger an execution. These executions will show up in the executions list, but not in the editor. ", "ndv.trigger.webhookNode.listening": "Listening for test event", "ndv.trigger.chatTrigger.openChat": "Open Chat Window", "ndv.trigger.webhookNode.formTrigger.listening": "Listening for a test form submission", diff --git a/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts b/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts index 4970ca4baf..531f0d8c71 100644 --- a/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts +++ b/packages/nodes-base/nodes/EmailReadImap/v1/EmailReadImapV1.node.ts @@ -73,9 +73,9 @@ const versionDescription: INodeTypeDescription = { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time an email is received, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time an email is received, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", diff --git a/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts b/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts index e5b46c584f..dd1afaca64 100644 --- a/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts +++ b/packages/nodes-base/nodes/EmailReadImap/v2/EmailReadImapV2.node.ts @@ -39,9 +39,9 @@ const versionDescription: INodeTypeDescription = { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time an email is received, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time an email is received, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then send an email to make an event happen. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time an email is received, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", diff --git a/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts b/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts index f2aa34824d..489288f0bb 100644 --- a/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts +++ b/packages/nodes-base/nodes/LocalFileTrigger/LocalFileTrigger.node.ts @@ -27,9 +27,9 @@ export class LocalFileTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then make a change to your watched file or folder. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", diff --git a/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts b/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts index 9d79437dd6..5fab13571c 100644 --- a/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts +++ b/packages/nodes-base/nodes/MQTT/MqttTrigger.node.ts @@ -34,9 +34,9 @@ export class MqttTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger an MQTT event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", diff --git a/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts b/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts index d2687afdbb..6e3760ede1 100644 --- a/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts +++ b/packages/nodes-base/nodes/Postgres/PostgresTrigger.node.ts @@ -32,9 +32,9 @@ export class PostgresTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger a Postgres event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you've finished building your workflow, activate it to have it also listen continuously (you just won't see those executions here).", diff --git a/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts b/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts index e1eca525ed..8bdf64081c 100644 --- a/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts +++ b/packages/nodes-base/nodes/RabbitMQ/RabbitMQTrigger.node.ts @@ -32,9 +32,9 @@ export class RabbitMQTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger a Rabbit MQ event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).", diff --git a/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts b/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts index 814ea59a35..acad85062b 100644 --- a/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts +++ b/packages/nodes-base/nodes/SseTrigger/SseTrigger.node.ts @@ -27,9 +27,9 @@ export class SseTrigger implements INodeType { header: '', executionsHelp: { inactive: - "While building your workflow, click the 'listen' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Once you're happy with your workflow, activate it. Then every time a change is detected, the workflow will execute. These executions will show up in the executions list, but not in the editor.", active: - "While building your workflow, click the 'listen' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", + "While building your workflow, click the 'test step' button, then trigger an SSE event. This will trigger an execution, which will show up in this editor.

Your workflow will also execute automatically, since it's activated. Every time a change is detected, this node will trigger an execution. These executions will show up in the executions list, but not in the editor.", }, activationHint: "Once you’ve finished building your workflow, activate it to have it also listen continuously (you just won’t see those executions here).",