@quoted seems to have no effect on validation result
See original GitHub issueCSV:
test-heading1,test-heading2,test-heading3
test-content1,test-content2,test-content3
CSV Schema:
version 1.1
@quoted
@totalColumns 3
@permitEmpty
@ignoreColumnNameCase
test-heading1: starts("test")
test-heading2: starts("test")
test-heading3: starts("test")
RESULT:
PASS
Issue Analytics
- State:
- Created 5 years ago
- Comments:8
Top Results From Across the Web
jsf 2 - quotes are lost from validation error message with ...
1 Answer 1 ... This is caused by the MessageFormat API which is under the covers being used for message formatting (substituting {0}...
Read more >FEC | Reporting | Validation errors explained
FECFile users: This error generally indicates that you have not closed the report. From the Reports window, highlight and right-click on your report,...
Read more >Error Explanations for The W3C Markup Validation Service
This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty,...
Read more >Your validation loss is lower than your training loss? This is ...
During validation and testing, your loss function only comprises prediction error, resulting in a generally lower loss than the training set. Image by...
Read more >Solutions to common product CSV import problems
This can be the result of Excel or another spreadsheet program adding curly quotes (smart quotes). These quotes need to be replaced with...
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
It shouldn’t matter either way, the CSV RFC says that quotes should only be used as necessary, but *nix tools tend to quote all columns by default. Just write your rules based on the data you actually want to see, ignoring any quotes. If we have opportunity we’ll try to merge #156 as @adamretter suggests, the you would use the quoted directive if all fields should be quoted.
OK. Will see if we can somehow squeeze that through.