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
In the current DataTable if we have a column with newline character (\n) and we want to export that column, it brokes the csv layout. Because, newline character is considered as newline in the exported csv also. To fix that, we can use custom exportFunction and replace \n with it's unicode version \u2028. I think doing that in the source code would make more sense because some people can have problem with that in the future.
Is your feature request related to a problem?
No response
Describe the solution you'd like
No response
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
melloware
added
Type: Enhancement
Issue contains an enhancement related to a specific component. Additional functionality has been add
and removed
Type: New Feature
Issue contains a new feature or new component request
Status: Discussion
Issue or pull request needs to be discussed by Core Team
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Jan 28, 2023
melloware
added
Type: Bug
Issue contains a defect related to a specific component.
and removed
Type: Enhancement
Issue contains an enhancement related to a specific component. Additional functionality has been add
labels
Jan 28, 2023
…ing csv (#4002)
* feat: replace newline character with its unicode version while exporting csv
Closes#4001
* feat: replace newline character with its unicode for column header
* chore: chain replace methods
* chore: replace one double quote with two double quotes for column header
Describe the feature you would like to see added
Hi,
In the current DataTable if we have a column with newline character (\n) and we want to export that column, it brokes the csv layout. Because, newline character is considered as newline in the exported csv also. To fix that, we can use custom exportFunction and replace \n with it's unicode version \u2028. I think doing that in the source code would make more sense because some people can have problem with that in the future.
Is your feature request related to a problem?
No response
Describe the solution you'd like
No response
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: