feat(data-collection): Port Rails log subscriber - #3034
Conversation
d8a5cd0 to
f24bdc4
Compare
5aff1d4 to
737323c
Compare
737323c to
0b56b5b
Compare
0b56b5b to
0f295fd
Compare
a94b458 to
b4853e5
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b4853e5. Configure here.
b4853e5 to
2926036
Compare
* Remove `ParameterFilter` usage completely * Nested payloads will now **not** be scrubbed (we will revisit this later if necessary)
2926036 to
6b771d6
Compare
| # @return [Hash] a new filtered hash, or an empty hash when collection is off | ||
| def filter(values, cookie: false) | ||
| return {} if mode == :off | ||
| return {} unless values.is_a?(Hash) |
There was a problem hiding this comment.
Why is this needed here? It can hide bugs or unwanted behaviors.
There was a problem hiding this comment.
failing gracefully since we cannot trust future call sites (or contract changes in Rails) is better than Sentry causing 500s in userland
There was a problem hiding this comment.
@sl0thentr0py OK but shouldn't this guard be located in places where we call filter? I'm just thinking that having it here may bite us potentially in the future.
There was a problem hiding this comment.
ok i'll move it to callsites

ParameterFilterusage completelyIssues