Allow the component and action to also be set by the library

[sixlive]

Description

By allowing the component and action to be set by the context as well as the additional parameters we can leverage it to easily set the component and action for the Laravel library.

$badger = Honeybadger::new([
    'api_key' => 'asdf',
    'handlers' => [
        'exception' => false,
        'error' => false,
    ],
], $client->make());

$badger->setComponent('HomeController');
$badger->setAction('index');

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

Outline the steps to test or reproduce the PR here.

> git pull --prune
> git checkout <branch>
> vendor/bin/phpunit

[joshuap]

This approach works for me. We have a similar approach for tags in our Ruby gem, where you can set the tags key in the context and those tags will get added to the error. This will basically add action and component as "special" keys for PHP context. We'll just need to be sure it's clearly documented so that people aren't surprised when using component as an arbitrary key in their context changes their error grouping. :)

[sixlive]

Maybe we should prefix them with honeybadger_ ?

[joshuap]

Yeah, I could go for that. Do you think we should delete the from the context when reading them, so they don't appear in the context section?

[sixlive]

@joshuap I made it much more simple. I added a setComponent and setAction method to the Honeybadger object. This still uses context under the hood but once we were talking about prefixing I didn't want to have to expose that implementation detail to a consumer. I also updated it so that we strip these values from the context since it really doesn't make sense to be in 2 places.

[joshuap]

Works for me. Thanks!