Add to-CSV conversion edge-case corpus - #319
Open
yangfanrc-cpu wants to merge 1 commit into
Open
yangfanrc-cpu wants to merge 1 commit into
yangfanrc-cpu wants to merge 1 commit into
Conversation
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
1 participant
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.
Adding a conversion test suite — 27 input shapes with byte-exact expected CSV output, and a runner that reports where two converters disagree.
https://github.com/yangfanrc-cpu/json-to-csv-edge-cases
This sits next to JSON Parsing Test Suite in spirit: that one pins down parsing, this one pins down what a conversion should emit. Every fixture is a small hand-built input plus the literal bytes expected back, covering the cases where implementations quietly diverge — nested objects and arrays, precision and leading zeros, embedded commas and newlines, unicode, duplicate and case-colliding keys, spreadsheet formula injection, and top-level array vs single object vs newline-delimited input.
tools/check.mjstakes any converter command, runs the corpus against it, and reports per-fixture agreement, keeping "differs only in line endings" separate from a real difference.One link, one line, and I am happy to shorten or reword it to match the house style.