Fix: Do not return violations with LogLevel.IGNORE #279
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.
Problem
Violations configured with LogLevel.IGNORE were still being returned from validation, causing 400 errors to be sent to clients even though these violations were meant to be ignored. Example being additional query params which is set to ignored here.
Solution
Filter out violations with LogLevel.IGNORE in both request and response validation before returning results. This ensures that violations explicitly marked to be ignored do not trigger 400 Bad Request responses.
Changes