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
My application uses console.dir to log very large/complex objects to the console for advanced users to explore. console.dir provides a better UX across most browsers than console.log (even though, in most modern browsers, console.log doesn't always attempt to convert values to a string).
Is there some workaround to tell PostHog to pretend console.dir is console.log, or even to disable rrweb on console.dir calls?
Thanks!
The text was updated successfully, but these errors were encountered:
Ah, no error message was produced, so I assumed that console.dir wasn't expected to work.
It seems like most of the problem is #968, there's just a small additional issue here of console.dir not returning (some?) internal errors. When I pass a BigInt to console.dir, I see only rrweb logger error: and no further message or context.
My application uses
console.dir
to log very large/complex objects to the console for advanced users to explore.console.dir
provides a better UX across most browsers thanconsole.log
(even though, in most modern browsers,console.log
doesn't always attempt to convert values to a string).Is there some workaround to tell PostHog to pretend
console.dir
isconsole.log
, or even to disable rrweb onconsole.dir
calls?Thanks!
The text was updated successfully, but these errors were encountered: