Add commentChar to CSV-DDF
See original GitHub issueThere are CSVs that exist in the wild that begin with some number of commented lines: example (45MB).
To support these kinds of files, we might want to have a new attribute as part of the dialect description: commentChar
.
See also: https://github.com/frictionlessdata/tabulator-py/issues/49
Issue Analytics
- State:
- Created 8 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Escape comment character (#) in git commit message [duplicate]
You can try and define a different character for comments in commit message: git config core.commentchar <another char>.
Read more >Git Commit Message file type respects git core.commentChar
Steps to Reproduce: Run the command git config core.commentChar ";"; Then run git commit --amend with vscode as GIT_EDITOR; Syntax ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@slythfox yes let’s keep it simple and refine as need arises.
If we keep it to “full line” comments as you both are describing then perhaps we should update CSV-DDF description to make that clear?
On the other hand, if there’s at least one CSV parser (e.g. JS csv-parse) that supports more than “full line” comments I imagine someone’s using it? So, alternatively, we could precisely define specific comment behavior, or add additional attributes to CSV-DDF and having the developer work with what configurations an underlying CSV parser supports.
I’m leaning on keeping it simple (i.e. update the CSV-DDF with clarification) and then add additional CSV-DDF comment attributes if a need arises