parseCsv with unqualified fields #97
Merged
Conversation
This file contains 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
|
Please fix your spacing to adhere to the current conventions. Spacing should be |
|
I think it's ok now. |
jprichardson
added a commit
that referenced
this pull request
Aug 6, 2014
parseCsv with unqualified fields
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.
Fix bug with the parseCsv function.
With this configuration:
qualifier: "
escape: "
lineDelimiter: \n
The field may not be encapsulated with the qualifier:
ie:
"my first field";"my second field" -> returns correct values
"my first field";my second field -> return only first field
"my ""cool field"" "; my second field -> return only first field