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
Far as I can tell, this is the behavior for the TLA:
@item evalScript(str, options = undefined)
Evaluate the string @code{str} as a script (global
eval). @code{options} is an optional object containing the following
optional properties:
@table @code
@item backtrace_barrier
Boolean (default = false). If true, error backtraces do not list the
stack frames below the evalScript.
@item async
Boolean (default = false). If true, @code{await} is accepted in the
script and a promise is returned. The promise is resolved with an
object whose @code{value} property holds the value returned by the
script.
@end table
For example, if I run eval("123") It actually gives me {"value": 123}. Is there a better way than directly assuming it as a object and accessing the value props?
Far as I can tell, this is the behavior for the TLA:
That means even if I do this:
For example, if I run
eval("123")
It actually gives me{"value": 123}
. Is there a better way than directly assuming it as a object and accessing the value props?Here's my workaround for now:
The text was updated successfully, but these errors were encountered: