Add `environment_name` in the README.md about honeybadger-ruby HOT 4 CLOSED

The same for the context, standalone applications don't have traditional request life cycle. A mention that you can specify the context for notifications without being global (for some life cycle) would be useful.

Honeybadger.notify e, { context: { my_context_key1: 'my key persisted only for this notification' } }

The README has only the global one.

Honeybadger.context { ... }

The Honeybadger.context for standalone applications can be dangerous, since it will not change automatically.

from honeybadger-ruby.

Hi Pablo, you're absolutely right - we do need better documentation on those features (and a few others, I'm sure). I would gladly accept pull requests with improved documentation if you feel inclined to pitch in, otherwise I'll be working on this over the next month or so. Thanks for reporting - let me know if you find anything else!

from honeybadger-ruby.

I've added this to our internal issue tracker since the gem documentation has now been moved here. Thanks!

from honeybadger-ruby.

@joshuap nice, thanks! 😄

from honeybadger-ruby.