Expose :value in SingleExceptionInterface

[jeffwidman]

👋 Hi from the team.

I'm attempting to migrate from sentry-raven to sentry-ruby:

• Migrate from sentry-raven to sentry-ruby dependabot/dependabot-core#7553

With Raven we performed some basic client-side sanitization of the exception message:
https://github.com/dependabot/dependabot-core/blob/65f1c2d24e88ac57ed8df980871446deb5ea2d94/updater/lib/dependabot/sentry.rb#L5-L21

The unit tests illustrate how it works:
https://github.com/dependabot/dependabot-core/blob/65f1c2d24e88ac57ed8df980871446deb5ea2d94/updater/spec/dependabot/sentry_spec.rb#L24-L91

Migrating this from Raven to sentry-ruby's before_send is straightforward. However, it looks like sentry-ruby doesn't expose :value on SingleExceptionInterface:

sentry-ruby/sentry-ruby/lib/sentry/interfaces/single_exception.rb

Line 14 in 7764384

attr_reader :type, :value, :module, :thread_id, :stacktrace

I see a recent change was made to expose :values on ExceptionInterface:

• Expose :values in ExceptionInterface #1843

So I'm guessing there's no technical reason this can't be made publicly writable? Just no one has raised a feature request for it yet?

[jeffwidman]

For now I've hacked around it using instance_variable_set but would much prefer having this publicly exposed:
https://github.com/dependabot/dependabot-core/pull/7553/files#diff-9ee3e6391d18c069de715a1740bb6239aa5f5c4734b3c03acd3455ba8bba3702R23-R24

[sl0thentr0py]

yea I can expose it, PR obviously welcome to speed it up

[jeffwidman]

Thanks, I put up a PR to expose it two weeks ago:

• Expose :value in SingleExceptionInterface #2072

[sl0thentr0py]

sorry didn't see that, need some time to catch up with this repo