Airbrake is basically wrapped around a begin rescue block… The app doesn’t break AND the error is sent to the application.
There are errors in apps that happen that you don’t care about, then there are show-stoppers. - Solution: rebuild a dashboard to ignore the errors or use airbrake to config their own errors.
?How do you decide what kinds of errors are important
after you instantite the credientials, you need to create the connections - learned this via the spec/client_spec
Keep running into the deep_merge undefined method. According to their specs, Airbreak assumes that the gems in the specs should be included in the library. They assume that people won’t be using this outside of rails, which is a big assumption.
HashieMashie- hashes behave as both as regular hash and as an object
Once the proper gems are required it works properly. If this library had corrected all of the dependencies in it’s stand along library, this would have been fine…
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21