The Designer IDE contains a built-in interface for debugging server-side low-code steps in Profound API and Rich Display File applications.
This Low-code debugger is different from the built-in Node.js debugger. The Low-code debugger does not pause the server when breakpoints are reached. Only debugged applications in specific debugging sessions are affected.
Debugging Profound.js and Node.js server-side code requires the use of the built in Node.js debug server (e.g. start the PJS instance with "node start.js --inspect") and a debugging client (e.g. Visual Studio Code or Chrome).
Debugging client-side JavaScript should be done using the web browser's built-in debugger (e.g. in Developer Tools in Firefox, Chrome, Edge, etc.).
The Low Code Debugger is available in Profound.js versions released after November, 2022.
Launching Debug Targets
When possible Designer will automatically determine how to launch a file opened for debugging. When Designer cannot determine how to launch a target for debugging, a user can manually run the API route or code in a separate application, browser tab, or window; add the debug session ID as the value for the dbgid URL parameter; then, the server will know to link that running application with the IDE's debugging session.
For example, if the debug session ID is deee2370-d58b-40b7-beb3-1efefab2e100, and the method to run a route is an HTTP POST, then to start running the application in debug mode, some other tool (PostMan, etc.) would need to send POST data to the URL and include a parameter, dbgid=deee2370-d58b-40b7-beb3-1efefab2e100 . E.g. https://example.com/run/yourWorkSpaceName/yourExpressRoute?dbgid=deee2370-d58b-40b7-beb3-1efefab2e100 .
Launching Profound API Routes for Debugging
To debug Profound API routes, start debugging a Profound API file, and then click on the "Execute" button in the "Test" tab on the right-middle panel of the API Designer.