Allow Boolean encoding to be governed by new BoolEncodingStrategy #10
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
This adds support for encoding boolean values in a variety of ways: - true/false (the default) - TRUE/FALSE - yes/no - YES/NO - 1/0 - Custom user-supplied strings
Rather than having a switch statement with identical ternary checks, move the true/false values to be computed properties on the strategy enum, which then simplifies the encode function.
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.
Booleans can now be formatted in one of several ways:
This is governed by a new strategy added to
CSVEncoderConfiguration. The default is.trueFalse, which is the same as the previous hardcoded encoding.Closes #2.