Allow new excluded_exceptions config

[mcfedr]

Adds new config option from getsentry/sentry-php#583

Shouldn't be merged until a new release is made.

I'd really appreciate if this was picked into the 0.8.x branch as well, as I'm currently having to use that version for old php support... its horrible but true...

[Jean85]

Thanks for the contibution!
To make this really work, we should require the next version of the client, so ^1.8.5 in the composer.json. Since this edit will make your fork unusable, feel free to commit it later, after that release is done on the client.

[Jean85]

Ehi @mcfedr, the Sentry SDK released a 1.9! Can you update your PRs?

[mcfedr]

Done, here is a new version with change to composer.json

[Jean85]

Thanks! Can you also open the same PR targeting the 1.x branch? I would like to backport it there too.

[Jean85]

2.0.3 of the bundle got released, the 1.9 client too and it's correcly required... LGTM! 👍

[mcfedr]

@Jean85 Maybe its time for a new version of the bundle as this isn't in 2.0.3? Its been quite a while now...

[Jean85]

Ouch, I totally forgot about this, thanks for reminding me!
I've added this to the changelog: d39d086

I hope to merge it ASAP.

[rvanlaak]

sentry-symfony started relying on the SDK's excluded_exceptions implementation, which is great but removes that the SDK is aware of Symfony exceptions that did get caught by default before.

We did not have any exceptions configured in excluded_exceptions yet, meaning that since skip_capture was removed in v3 the defaults the implementation used to rely on are gone.

When upgrade to v3, Sentry starts capturing HttpExceptionInterface instances. Did create PR #269 to restore the old behavior.