-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support deep keys #137
Comments
Thanks for filing this! I think we already support that on notifier level (if you filter just {
not_foo: {
not_foo_again: {
foo: 'will be filtered'
}
}
} But in this regard our API is probably indeed incompatible. I guess it's better to document this and ignore |
doing this atm ... just a evil trap that the docs say 'put filter into blacklist' and then they do not work the same way ... which ends up leaking secrets into airbrake ... not fun :( |
Sorry about that. I was simply unaware of the |
would you accept a PR to add this feature ? ... I think it's pretty useful :) |
Depends on the implementation. If there's a neat way to implement this, then why not? However our current policy is to filter out every matching key, no matter how deep it is. We also support whitelists. This might make the implementation harder. Without special cases the code for truncation is nice, fast and tidy. TL;DR Go for it, but it might be harder than you think :P |
took a look ... would mean rewriting filtering logic ... and make it a bunch slower ... so not doing it ... |
Fixes airbrake/airbrake-ruby#137 (Support deep keys)
Fixes airbrake/airbrake-ruby#137 (Support deep keys)
rails filter_parameters allows
foo.bar
meaningfoo[bar]
which is not compatible with airbrakes blacklist filter
so please either:
The text was updated successfully, but these errors were encountered: