by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Guy Boertje
    @guyboertje
    Hi - you may not know this but I grew up in Durban - emigrated to the UK in 1986
    Regarding the public API including info, debug i.e the same as Logger - its because Rollbar recently changed their API to be the same as Logger.
    Kenneth Kalmer
    @kennethkalmer
    Howzit Guy! I must admit, I had my suspicions that you’re from these parts :)
    Oh wow, will have a look at the Rollbar API and see why they did it
    I still think Safely should be focussed on the general exception tracking case, at least at first
    Guy Boertje
    @guyboertje

    By forking Safely and extending it to support non-exception based reporting, I was trying to remove the need to do:

    Rollbar.error e
    Logger.error e

    where my co-workers and

    I would leave out one or other line unintentionally.
    Guy Boertje
    @guyboertje
    and
    message, info = 'api returned:', response: response
    Rollbar.info message, info
    Logger.info message, info
    into just:
    Safely.info 'api returned:', reponse: response
    Kenneth Kalmer
    @kennethkalmer
    Aha
    ok, I see exactly what you mean
    Kenneth Kalmer
    @kennethkalmer
    I like where you’re going, lets stick with exception handling first and then roll in the logging API
    Guy Boertje
    @guyboertje
    In the adapters for the services that only support exception reporting, I would consider a noop methods Module mixin.
    Kenneth Kalmer
    @kennethkalmer
    or throwing an exception?
    the last thing I want is to surprise users
    or something in between… you configure an exception adapter, and a logging adapter