You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2.Launch it in the terminal and see the correct output:
Launch it in the debugger and see the wrong output:
So when running in the debugger then console.log() without parameters and console.log("") with an empty string parameter does not generate an empty output line. But logging a single space character works.
Does this issue occur when all extensions are disabled?: Yes
This problem is similar to #24308 I reported last year. In this issue I reported that empty lines where sometimes ignored. Now they are always ignored. So looks like the bug wasn't fixed properly.
The text was updated successfully, but these errors were encountered:
The issue here is that I am not getting an output event from the debug adapter for those empty outputs -> forwarind first to @roblourens to investigate
There might be something that we are doing wrong on the ui end on top of that, but this is the initial issue, so it would be great if @roblourens could check on the adapter side. Thanks
Steps to Reproduce:
2.Launch it in the terminal and see the correct output:
So when running in the debugger then
console.log()
without parameters andconsole.log("")
with an empty string parameter does not generate an empty output line. But logging a single space character works.Does this issue occur when all extensions are disabled?: Yes
This problem is similar to #24308 I reported last year. In this issue I reported that empty lines where sometimes ignored. Now they are always ignored. So looks like the bug wasn't fixed properly.
The text was updated successfully, but these errors were encountered: