Repository navigation
Fix filtering edge cases and validation gaps - #44
Merged
Merged
Conversation
Member
Author
|
QA — 2026-10-21, commit
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nested query parameters, short Basic credentials and deeply nested Symbols could reach log output without redaction. A filter that raised could expose its value or repeatedly log/report its own failures.
This change closes those gaps, filters values when a matcher fails, and prevents recursive error handling. It also applies size limits before walking omitted values, avoiding unnecessary recursive copies of large inputs.
Validation on
06738d4:task ci RAILS_VERSION=8.1.2andcd docs && pnpm checkpassed: 508 Ruby tests, 184 JavaScript tests, five static-site tests and 14 browser tests.Summary by CodeRabbit
Bug Fixes
Documentation
Chores