From b83760a3247737a68251138b3cafcd42d7c42e10 Mon Sep 17 00:00:00 2001 From: haru0017 Date: Thu, 9 Apr 2026 10:04:22 +0900 Subject: [PATCH] replace tailorErrorMessage with standard error --- docs/reference/api/js-scripting.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/api/js-scripting.md b/docs/reference/api/js-scripting.md index 9ee25e9..f2c1f98 100644 --- a/docs/reference/api/js-scripting.md +++ b/docs/reference/api/js-scripting.md @@ -8,7 +8,7 @@ tabs: (() => { // throws an error if no heroes found if (args.characters.edges.length < 0) { - throw new TailorErrorMessage("No heroes found") + throw new Error("No heroes found") } return { "success": true, @@ -28,7 +28,7 @@ tabs: (() => { // throws an error if no heroes found if (args.characters.edges.length < 0) { - throw new TailorErrorMessage("No heroes found") + throw new Error("No heroes found") } return { "success": true, @@ -249,7 +249,7 @@ Here are some examples of where you can utilize JavaScript: You can use `PostHook` field in the Pipeline to return the object that can be used in the later steps. -Throwing a `TailorErrorMessage` in a pipeline step causes the pipeline execution to halt when the error is caught, and the API then returns the error message as the response. +Throwing an `Error` in a pipeline step halts the execution. The API returns the error in the format `: ` (e.g., `Error: No heroes found`). **Example**: