Fix CSV field escaping - #64
Open
juangaitanv wants to merge 1 commit into
Open
Conversation
juangaitanv
marked this pull request as ready for review
August 5, 2026 10:57
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
2 participants
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.
Summary
Fix CSV serialization so every textual field is quoted when it contains a comma, quote, CR, or LF. The previous formatter only escaped the code field, so valid finding values such as a path containing a comma shifted subsequent columns and produced malformed CSV.
Add a focused escaping unit test and a CLI regression test that scans a Python file whose path contains a comma. No dependency was added, and ordinary CSV output remains unchanged.
Related issue
None.
Checklist
make cipasses locally (the same command CI runs — see CONTRIBUTING.md)make bootstraponce so pre-commit/pre-push hooks are active