Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

The Low Code Debugger is available in Profound.js versions released after November, 2022version 6.0.0.



Launching Debug Targets

When possible Designer will automatically determine how to launch a file opened for debugging. Debug a low-code application or Profound.js API file by opening it in Designer; click the Launch menu; click Debug Low-code:

Image Added


The debugging panel will appear with low-code routines. Click a routine to see the low-code steps. Click a low-code step to set a breakpoint for it:

Image Added


Click the green "play" icon to run the low-code app in debug mode. A Rich Display file will run in a new Designer tab:

Image Added


Launching Profound API Routes in Debug:

Open the API file in Designer. click "Debug Low-code" in the Launch menu if you have not already. In the Debug panel click on the API Route you want to debug, and set the desired breakpoints. Click the green "play" icon, and the API "Test" panel should become active:

Image Added


Scroll to the Execute button, and click it.


Manually running a debug target using the Debug Session ID:

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.

...