CSV export configurable delimiter
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Is your feature request related to a problem? Please describe.
Export to CSV automatically uses comma as delimiter, which is pretty much always the worst idea of all.
A table entry simply needs to allow text input and a user entering a common sentence, which, by normal grammatically means, now and then requires to enter a comma.
The export of such data is immediately unsubale when exported to CSV.
I looked around in the Tables app, if there is any setting to change that to say semicolon, which is a lot more robust, but couldn't find one.
Even better would be a possibility for export to .xlsx , which immediately eliminates all potential delimiter related issues...
Edit:
I just figured, that Microsoft Excel uses the quotes surrounding a sentence with a comma to ensure all fits into one cell.
However, other office suites, like Onlyoffice, does not do that and therefore fails on import.
Describe the solution you'd like
A way to modify the delimiter character for CSV export.
Either globally or per user.
Even better would be export to Excel format .xlsx
Describe alternatives you've considered
There isn't any, which was obvious to me.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating the Tables app's CSV export entry point and the controls that trigger it, then determine where an export delimiter could be configured globally or per user. Done means CSV exports use the selected delimiter reliably; XLSX export is an additional, broader option rather than a defined requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100