airbrake/airbrake — comment on commit 477bbb51c99540fe76e60db2e14f2fb624320f54
File: lib/airbrake.rb line 140
By aiwilliams:

This change breaks the feature described in the README.md/'Going Beyond Exceptions' which indicates we may call:

```ruby
Airbrake.notify(
:error_class => "Special Error",
:error_message => "Special Error: #{e.message}",
:parameters => params
)
```

An error is generated:

```bash
undefined method `backtrace' for #
# ./vendor/ruby/1.9.1/gems/airbrake-3.0.5/lib/airbrake/notice.rb:223:in `from_exception'
# ./vendor/ruby/1.9.1/gems/airbrake-3.0.5/lib/airbrake/notice.rb:208:in `exception_attribute'
# ./vendor/ruby/1.9.1/gems/airbrake-3.0.5/lib/airbrake/notice.rb:96:in `initialize'
# ./vendor/ruby/1.9.1/gems/airbrake-3.0.5/lib/airbrake.rb:142:in `new'
# ./vendor/ruby/1.9.1/gems/airbrake-3.0.5/lib/airbrake.rb:142:in `build_notice_for'
# ./vendor/ruby/1.9.1/gems/airbrake-3.0.5/lib/airbrake.rb:103:in `notify'
```

Notice that, according to the README.md, the first argument to ```notify``` is a Hash.

I need the feature because we are sending notices even when there is no exception. Am I missing an assumed practice of instead raising a custom exception?