scripts run with 'discard' option set to true are shown as [temp] during debug with Visual Studio Code

[77it]

trying to debug some scripts, I found that scripts run with Evaluate or Execute discard option set to true always pollute the <node internals> section of Visual Studio Code while debugging.

the only difference between discarded and not discarded scripts is that discarded scripts has "[temp]" add to them.

follows an image with the <node internals> section of Visual Studio Code

[ClearScriptLib]

Hi @stefano77it,

This behavior is by design, going back to a time when ClearScript only supported Windows script engines. Back then discard had more of an effect, as temporary scripts would disappear from the debugger user interface after execution.

V8 and modern debuggers don't honor discard, but the "[temp]" suffix remains. Is that a serious issue for you?

Thanks!

[77it]

It's not a serious issue, because using Invoke the <node internals> section of Visual Studio Code is not polluted with the calls to functions (that in my case are hundreds).

However, I think you should update the API documentation of Evaluate and Execute because both contain the phrase

Discarding this document removes it from view but has no effect on the script engine

which is no longer aligned to V8 and modern debuggers.

[ClearScriptLib]

Documentation updated in Version 6.0.1.