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
We don't always want to add context to an error - sometimes console.error(new Error('bang')) is fine. If you do that, however, it still tries to add the context to the message field, e.g.
If no context is provided, it should leave the message field alone, e.g. {"level":"error","message":"bang", ...}
I believe this should remove that leading -, but there are actually two spaces before the hyphen, so it wouldn't catch it. There are always two spaces before the hyphen, even when there is context.
Thanks!
The text was updated successfully, but these errors were encountered:
Version: 2.9.0
We don't always want to add context to an error - sometimes
console.error(new Error('bang'))
is fine. If you do that, however, it still tries to add the context to themessage
field, e.g.outputs
With context, it works fine, e.g.
outputs
If no context is provided, it should leave the
message
field alone, e.g.{"level":"error","message":"bang", ...}
I believe this should remove that leading
-
, but there are actually two spaces before the hyphen, so it wouldn't catch it. There are always two spaces before the hyphen, even when there is context.Thanks!
The text was updated successfully, but these errors were encountered: