Replies: 1 comment
-
Thanks for your inputs! This is indeed a trade-off: for the human eye, data is so much more clean and readable without all the quotes. It's one of the things I like about CSV. But it introduces relatively complex rules about when quotes are required. For parsers, ease of understanding, and hence overall robustness, it's easier to have mandatory quotes. Good point, let's rethink optional quotes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Interesting concept for sure, JSON files are easy to work with but can sometimes be quite large so the inclusion a csv like format is intriguing. I understand the desire to make quotes around keys and strings optional, but I think that makes the files very prone to user error.
For example in the playground the string First Avenue does not require the double quotes, but the string 1st Avenue does since it starts with an integer. When modifying a file manually it is easy to make mistakes such as these, even for experienced users. I would therefore make it as fool proof as possible by enforcing double quotes around all keys and strings, just as the JSON file format does.
Beta Was this translation helpful? Give feedback.
All reactions