Drop to_hash in SentryParameterFilter to support sentry-ruby v6

[shogo-hta]

Summary

• Changed SentryParameterFilter#process from hash access (event[:request][:data], etc.) to direct object access on Sentry::Event / Sentry::RequestInterface (event.request.data, etc.)
• Addresses the deprecation of to_hash in sentry-ruby v5 and its removal in v6
• Callers must update from filter.process(event.to_hash) to filter.process(event) (breaking change — major version bump planned)

Test plan

• Updated spec/blouson/sentry_parameter_filter_spec.rb to use Sentry::ErrorEvent + Sentry::RequestInterface objects instead of plain hashes
• Confirmed all 7 tests pass

🤖 Generated with Claude Code

[koheisg]

@os0x Sorry to jump in from the side, but I ran into the same issue. It might be helpful to update the sample code in the README as well. Apologies for only leaving a comment instead of sending a patch myself.

thanks a lot!

[Copilot]

Pull request overview

Updates Blouson’s SentryParameterFilter to operate directly on Sentry::Event / Sentry::RequestInterface objects instead of event.to_hash, aligning with sentry-ruby v6 where to_hash is removed.

Changes:

• Refactored SentryParameterFilter internals to use event.request.* and event.extra rather than hash access.
• Updated specs to construct and assert against real Sentry::ErrorEvent + Sentry::RequestInterface objects.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
lib/blouson/sentry_parameter_filter.rb	Switches filtering logic from hash-based event access to Sentry object accessors.
spec/blouson/sentry_parameter_filter_spec.rb	Reworks test setup/assertions to use Sentry event/request objects and validate the new behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[nekketsuuu]

📝 getsentry/sentry-ruby#2351

[nekketsuuu]

Mostly LGTM. Would you please add a lower bound of sentry-ruby gem in gemspec?

[nekketsuuu]

Memo: I think it's okay to leave this condition as is, but it seems that Sentry::RequestInterface expects data is a Hash: https://github.com/getsentry/sentry-ruby/blob/a1c52820777d5ddb151ba66fd55cced0732730fd/sentry-ruby/lib/sentry/interfaces/request.rb#L24-L26

[shogo-hta]

Although it's annotated as @return [Hash] , looking at the read_data_from implementation, there are several cases where it returns a String:

• Non-form-data requests (e.g. JSON): request.body.read → String
• Non-rewindable body: "Skipped non-rewindable request body" → String
• IOError: e.message → String

So the data.is_a?(String) check is still necessary.

[nekketsuuu]

nit: I think this should be written in CHANGELOG instead of README

[shogo-hta]

This is an important breaking change, so it would be good to document it in both the README and CHANGELOG.

[shogo-hta]

Would you please add a lower bound of sentry-ruby gem in gemspec?

Done! I've added >= 6.0 as the lower bound of sentry-ruby in gemspec.
Note that it's a development_dependency since SentryParameterFilter is an optional feature that users need to explicitly require.

[shogo-hta]

Since it's a development_dependency, users can still bundle install with sentry-ruby v5 or earlier.
We could address this by raising an error at require time if the sentry-ruby version is too old.
like,

require 'sentry-ruby'
gem_version = Gem.loaded_specs['sentry-ruby']&.version
if gem_version && gem_version < Gem::Version.new('6.0')
  raise "blouson's SentryParameterFilter requires sentry-ruby >= 6.0 (you have #{gem_version})"
end

What do you think?

[nekketsuuu]

I think it is sufficient to mention it in the changelogs. In any case, it will cause an error because of to_hash.

[nekketsuuu]

Thanks for your fix!