Repository navigation
feat(csv-stringify): preserve structure with relaxed quotes - #559
Merged
Merged
Conversation
wdavidw
force-pushed
the
feat/stringify-relax-quotes
branch
from
November 5, 2026 12:56
0c63634 to
e678be7
Compare
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.
Disabling quoting can turn one field into several fields or records. This follows the requested alternative in #558: restore the previous disabled-quote behavior and make relaxed quotes an explicit
relax_quotesoption, defaulting tofalse.With
relax_quotes: true, interior quotes stay unchanged in unquoted fields. Fields containing delimiters, record delimiters, or leading quotes still receive enclosing quotes and normal escaping. Leading quotes after whitespace are also enclosed so a parser using trim does not mistake them for the start of a quoted field. Explicit quoting selectors continue to take precedence.The normal RFC 4180 quoting behavior remains the default. Relaxed output requires the matching parser option. The option is available in TypeScript and field-level cast settings, with a sample showing which fields remain enclosed. Generated distributions are left to the release build process.