When I was writing the previous post, I found numerous scenarios which JSON Table Editor unable to handle. These scenarios are based on three factors:

1. Separator. Is the column separated by comma? Or tabs? Or fixed length?
2. Name. Does the data has the column names in the beginning? Does these names only contained in one line? Or it’s spread across multiple lines?
3. Start Location. Does the data started from the first line? Or we need to ignore a number of lines before arrive at the data?
4. End Location. Does the data all the way to the end of the file? Or there are non-data lines at the end of the file?

The earlier version of CSV-handling functionality didn’t consider above factors. It simply assume that your CSV is comma-separated (Duh!). It has header on the first line. And the data goes all the way until the end of the file. Which is way it might not for your use-case.

The good thing is, I have take these factors into consideration. Without further ado, below are some of the test scenarios:

1. Standard CSV file. Source file: LINK. Loaded in Editor: LINK
2. Standard CSV file without header. Source file: LINK. Loaded in Editor: LINK
3. TAB-separated text file without header. Source file: LINK. Loaded in Editor: LINK
4. Text file with fixed-length columns. Source file: LINK. Loaded in Editor: LINK
5. Fixed-length columns text file where the header is not on the first line. Source file: LINK. Loaded in Editor: LINK
6. Fixed-length columns text file where the header is multi-lines. Source file: LINK. Loaded in Editor: LINK

What do you think? Is there any other factors that I can incorporate into the Editor?

Incoming Search

csv, data, json, json-table-editor