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
Items logged using Rollbar.warn(), Rollbar.error(), and Rollbar.critical(), aren't categorized as the correct level depending on the type of the dynamic error argument.
For instance, if I execute Rollbar.warn('Test error', Stacktrace.empty);, the resulting item is set to the info level in my project. If I instead excecute Rollbar.warn(Exception('Test error'), Stacktrace.empty);, the item is correctly set to the warning level.
Similar things seem to happen when using Rollbar.error() - they end up being set to info if a String is passed, and warning if an Exception is passed. I assume the only way to get the result I would expect is to pass an Error object.
This behavior is bizarre and confusing, and on top of that the documentation provided no help when I began trying to find out why the items weren't the correct levels based on the methods I was using.
The text was updated successfully, but these errors were encountered:
Items logged using
Rollbar.warn()
,Rollbar.error()
, andRollbar.critical()
, aren't categorized as the correct level depending on the type of thedynamic error
argument.For instance, if I execute
Rollbar.warn('Test error', Stacktrace.empty);
, the resulting item is set to theinfo
level in my project. If I instead excecuteRollbar.warn(Exception('Test error'), Stacktrace.empty);
, the item is correctly set to thewarning
level.Similar things seem to happen when using
Rollbar.error()
- they end up being set toinfo
if aString
is passed, andwarning
if anException
is passed. I assume the only way to get the result I would expect is to pass anError
object.This behavior is bizarre and confusing, and on top of that the documentation provided no help when I began trying to find out why the items weren't the correct levels based on the methods I was using.
The text was updated successfully, but these errors were encountered: