You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have exported a CSV file from a google spreadsheet, whereby some cells contain line breaks. When reading that file using yq these line breaks are removed, although I'd like to keep them. This happens no matter which output format I choose using the -o command line flag.
Version of yq: 4.42.1
Operating system: mac
Installed via: homebrew
Input Yaml
test.csv:
Header1,Header2
"Some data with a
line break",Some data without a line break
Command
yq test.csv
Actual behavior
Header1,Header2
Some data with a line break,Some data without a line break
Expected behavior
Header1,Header2"Some data with aline break",Some data without a line break
Additional context
As said before, this also happens when converting the content to YAML, JSON, ... In my use case I would need a JSON output including \ns to represent line breaks, although I'd be open to solve that differently. However, by just ignoring the line breaks in this case it is impossible to solve my current task.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have exported a CSV file from a google spreadsheet, whereby some cells contain line breaks. When reading that file using
yq
these line breaks are removed, although I'd like to keep them. This happens no matter which output format I choose using the-o
command line flag.Version of yq: 4.42.1
Operating system: mac
Installed via: homebrew
Input Yaml
test.csv:
Command
Actual behavior
Expected behavior
Additional context
As said before, this also happens when converting the content to YAML, JSON, ... In my use case I would need a JSON output including
\n
s to represent line breaks, although I'd be open to solve that differently. However, by just ignoring the line breaks in this case it is impossible to solve my current task.The text was updated successfully, but these errors were encountered: