Fixes bug #69181 (csv parsing drops newlines within fields with SplFileObject::DROP_NEW_LINE) #1148
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.
This pull request fixes buggy behaviour when using
SplFileObject
to work with CSV files.According to the documentation, the
DROP_NEW_LINE
flag drops newlines at the end of a line. http://php.net/manual/en/class.splfileobject.php#splfileobject.constants.drop-new-lineHowever, even though CSV files are obviously stored with new lines at the end of each line, the fields within the CSV can also contain any number of newline characters, as long as they are quoted. In this case, the bug appears, as the DROP_NEW_LINE flag causes c function
strcspn
to remove the first, and only the first, newline from the entire row of fields.My solution is to ignore the
strcspn
function when parsing CSV files, because if there are any newlines within fields, the fields MUST be delimited, therefore no newlines should be dropped within the delimiters.