honeybadger 5.0.2 → 5.1.0

data/LICENSE

@@ -1,19 +1,19 @@
-Copyright (c) 2015 Honeybadger Industries LLC
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+Copyright (c) 2015 Honeybadger Industries LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -1,57 +1,57 @@
-# Honeybadger for Ruby
-
-![Ruby](https://github.com/honeybadger-io/honeybadger-ruby/workflows/Ruby/badge.svg)
-![JRuby](https://github.com/honeybadger-io/honeybadger-ruby/workflows/JRuby/badge.svg)
-[![Gem Version](https://badge.fury.io/rb/honeybadger.svg)](http://badge.fury.io/rb/honeybadger)
-
-This is the notifier gem for integrating apps with the :zap: [Honeybadger Exception Notifier for Ruby and Rails](http://honeybadger.io).
-
-When an uncaught exception occurs, Honeybadger will POST the relevant data to the Honeybadger server specified in your environment.
-
-## Documentation and Support
-
-For comprehensive documentation and support, [check out our documentation site](https://docs.honeybadger.io/ruby/index.html).
-
-## Changelog
-
-See https://github.com/honeybadger-io/honeybadger-ruby/blob/master/CHANGELOG.md
-
-## Development
-
-Pull requests are welcome. If you're adding a new feature, please [submit an issue](https://github.com/honeybadger-io/honeybadger-ruby/issues/new) as a preliminary step; that way you can be (moderately) sure that your pull request will be accepted.
-
-If you're integrating your gem/open source project with Honeybadger, please consider submitting an official plugin to our gem. [Submit an issue](https://github.com/honeybadger-io/honeybadger-ruby/issues/new) to discuss with us!
-
-We use [YARD](https://yardoc.org/) to document our API. Classes and methods which are safe to depend on in your gems/projects are marked "Public". All other classes/methods are considered internal and may change without notice -- don't depend on them! If you need a new public API, we're happy to work with you. [Submit an issue](https://github.com/honeybadger-io/honeybadger-ruby/issues/new) to discuss.
-
-### To contribute your code:
-
-1. Fork it.
-2. Create a topic branch `git checkout -b my_branch`
-3. Make your changes and add an entry to the [CHANGELOG](CHANGELOG.md).
-4. Commit your changes `git commit -am "Boom"`
-5. Push to your branch `git push origin my_branch`
-6. Send a [pull request](https://github.com/honeybadger-io/honeybadger-ruby/pulls)
-
-### Running the tests
-
-We're using the [Appraisal](https://github.com/thoughtbot/appraisal) gem to run
-our [RSpec](https://www.relishapp.com/rspec/) test suite against multiple
-versions of [Rails](http://rubyonrails.org/).
-
-* The unit test suite can be run with `rake spec:units`.
-* The integration test suite can be run with `rake spec:features`.
-* The combined suite can be run with `rake`.
-
-### Releasing
-
-To release a new [patch] version:
-
-1. With a clean working tree, use `rake bump:patch` to bump the version and stage the changes (you can make additional manual changes at this point if necessary).
-2. Use `rake release` to run the tests, commit/tag the release, build the gem, and push to GitHub/RubyGems.
-
-See `rake -T` for additional tasks.
-
-### License
-
-The Honeybadger gem is MIT licensed. See the [LICENSE](https://raw.github.com/honeybadger-io/honeybadger-ruby/master/LICENSE) file in this repository for details.
+# Honeybadger for Ruby
+
+![Ruby](https://github.com/honeybadger-io/honeybadger-ruby/workflows/Ruby/badge.svg)
+![JRuby](https://github.com/honeybadger-io/honeybadger-ruby/workflows/JRuby/badge.svg)
+[![Gem Version](https://badge.fury.io/rb/honeybadger.svg)](http://badge.fury.io/rb/honeybadger)
+
+This is the notifier gem for integrating apps with the :zap: [Honeybadger Exception Notifier for Ruby and Rails](http://honeybadger.io).
+
+When an uncaught exception occurs, Honeybadger will POST the relevant data to the Honeybadger server specified in your environment.
+
+## Documentation and Support
+
+For comprehensive documentation and support, [check out our documentation site](https://docs.honeybadger.io/lib/ruby/).
+
+## Changelog
+
+See https://github.com/honeybadger-io/honeybadger-ruby/blob/master/CHANGELOG.md
+
+## Development
+
+Pull requests are welcome. If you're adding a new feature, please [submit an issue](https://github.com/honeybadger-io/honeybadger-ruby/issues/new) as a preliminary step; that way you can be (moderately) sure that your pull request will be accepted.
+
+If you're integrating your gem/open source project with Honeybadger, please consider submitting an official plugin to our gem. [Submit an issue](https://github.com/honeybadger-io/honeybadger-ruby/issues/new) to discuss with us!
+
+We use [YARD](https://yardoc.org/) to document our API. Classes and methods which are safe to depend on in your gems/projects are marked "Public". All other classes/methods are considered internal and may change without notice -- don't depend on them! If you need a new public API, we're happy to work with you. [Submit an issue](https://github.com/honeybadger-io/honeybadger-ruby/issues/new) to discuss.
+
+### To contribute your code:
+
+1. Fork it.
+2. Create a topic branch `git checkout -b my_branch`
+3. Make your changes and add an entry to the [CHANGELOG](CHANGELOG.md).
+4. Commit your changes `git commit -am "Boom"`
+5. Push to your branch `git push origin my_branch`
+6. Send a [pull request](https://github.com/honeybadger-io/honeybadger-ruby/pulls)
+
+### Running the tests
+
+We're using the [Appraisal](https://github.com/thoughtbot/appraisal) gem to run
+our [RSpec](https://www.relishapp.com/rspec/) test suite against multiple
+versions of [Rails](http://rubyonrails.org/).
+
+* The unit test suite can be run with `rake spec:units`.
+* The integration test suite can be run with `rake spec:features`.
+* The combined suite can be run with `rake`.
+
+### Releasing
+
+To release a new [patch] version:
+
+1. With a clean working tree, use `rake bump:patch` to bump the version and stage the changes (you can make additional manual changes at this point if necessary).
+2. Use `rake release` to run the tests, commit/tag the release, build the gem, and push to GitHub/RubyGems.
+
+See `rake -T` for additional tasks.
+
+### License
+
+The Honeybadger gem is MIT licensed. See the [LICENSE](https://raw.github.com/honeybadger-io/honeybadger-ruby/master/LICENSE) file in this repository for details.

data/TROUBLESHOOTING.md

@@ -1,3 +1,3 @@
-# Troubleshooting
-
-Troubleshooting instructions have been moved to our [documentation site](http://docs.honeybadger.io/ruby/support/troubleshooting.html)!
+# Troubleshooting
+
+Troubleshooting instructions have been moved to our [documentation site](http://docs.honeybadger.io/ruby/support/troubleshooting.html)!

data/bin/honeybadger

@@ -1,5 +1,5 @@
-#!/usr/bin/env ruby
-
-require File.expand_path('../../lib/honeybadger/cli.rb', __FILE__)
-
-Honeybadger::CLI.start(ARGV)
+#!/usr/bin/env ruby
+
+require File.expand_path('../../lib/honeybadger/cli.rb', __FILE__)
+
+Honeybadger::CLI.start(ARGV)