Need Javascript debugger
799
Views
10
Comments
New
Debugger

we should have javascript debugger capability on service studio as well, So that we can debug on service studio itself.



Changed the category to
Debugger

Isn't that easily done with the dev tools of your browser?

Well That depends on Browser. Some companies only allow to use IE.

Merged this idea with 'Introducing breakpoint inside JavaScript editor.' (created on 25 Apr 2023 10:51:19 by Thizwilondi Malupa)

I think it would be great to have the ability to set a breakpoint inside the javascript editor . This can help in case where one has many lines of  JavaScript code that is not producing correct output , then it would be easy to debug the code. 

Hi Thizwilondi,

That is why each browser has DevTools! that is how you debug your JavaScript, HTML and CSS.

Don't expect OutSystems to rebuild this into Service Studio.

Regards,

Daniel

I hear Daniel on his comment about being able to use the Browser. However, other IDEs do have such features built into them such as VSCode so I don't think it is unreasonable to expect OutSystems to do the same.

It would be very convenient to be able to debug in OutSystems as per usual and when it goes into a JS element then continue to debug into that rather than it just being a black box (unable to see what's happening in there) and having to swap to the browser debugger to see what's happening there.

This would also simplify it for people who are not savvy with the browser dev tools. Not that it should be an excuse but for a low-code platform many users may not know how to use them.

Merged this idea with 'Debugging JavaScript component' (created on 15 Jun 2023 12:23:50 by Aman Singh Rajput)

The debugger doesn't allow to debug JS component. 

If during debugging the flow goes to a JS component having an error, only an error message is triggered with the highest level error. This make it hard to debug long JS codes.

Suggestion:

Maybe a light weight debugger made especially for the JS component and shows in which line the error occurred as well as the traceback route .


Changed the category to
Debugger