mirror of
https://github.com/ToolJet/ToolJet
synced 2026-04-22 22:17:55 +00:00
bdfe3270e2
* docs: jira * docs: formatting + Client Credentials grant type * docs: connection string pgsql * docs: parameterized queries mysql * docs: parameterized queries in PostgreSQL * docs: update mysql example * docs: TJDB sql editor * docs: add metadata to REST API * docs: add, update postgresql media * docs: add metadata to graphql * docs: update parameterized queries * docs: add parameterized queries for mssql * docs: add SSL Cert to mysql * docs: TJDB SQL restricted commands * docs: update JIRA token location * docs: update delete issue example * docs: update find user by query example * docs: remove session id from get assignable users * docs: use correct image for get issues for board * docs: update create issue example * docs: update delete issue media * docs: update assignable users media * docs: update examples * docs: update key desc * docs: v2.68.0-Beta
1.4 KiB
1.4 KiB
| id | title |
|---|---|
| intentionally-fail-js-query | Intentionally Throwing an Error in RunJS for Debugging |
In this step-by-step guide, we'll walk you through the process of creating a RunJS query that intentionally throws an error for debugging purposes.
Creating the Error-Throwing RunJS Query
-
Create a new RunJS query by clicking the
+ Addbutton on the query panel. -
Paste the following code into the RunJS query editor. This code utilizes the
ReferenceErrorconstructor to intentionally generate an error.throw new ReferenceError('This is a reference error.');
Adding an Event Handler for Failure
-
Now, enhance the query by adding an event handler that will display an alert when the query fails.
-
Click the "Run" button to execute the query and observe the intentional error being thrown.
Refer to the screencast below:
By following these steps, you can effectively simulate errors in your RunJS queries, aiding in the debugging process and improving the overall robustness of your code.