feat: DH-21079: support escape characters#309
Merged
kosak merged 3 commits intodeephaven:mainfrom Jan 15, 2026
Merged
Conversation
3a4e124 to
b29d8d4
Compare
4122122 to
2210d2f
Compare
2210d2f to
7a66d24
Compare
lbooker42
reviewed
Jan 15, 2026
lbooker42
approved these changes
Jan 15, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
NOTE TO REVIEWERS: This PR is downstream of #308. It will be easier to read this PR once that one is merged.Add opt-in support for an escape character. This allows two features:
\b \t \n \r \f),)For example, if
\is enabled as the escape character inCsvSpecs, then this input will be parsed with an embedded newlinehello\nthereLikewise, this input will be parsed as two cells: "hello, world" and "42"
hello\, world, 42