You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where the delimiter is wrongly detected or possibly, the rows are too big, the previewer tries to fetch too much data from the file, which of course is terrible if someone is on a mobile data connection. To solve this a (configurable) data limit has to be applied to the JavaScript that fetches the initial rows from the CSV file.
Correct! But it was done in the maint-1.0.0alpha branch, so I opened a "forward-port" (?) PR at #185.
The solution differs from the one I described in the initial issue since it applies a strict threshold as a validation check for previewing the file (but is good enough for now).
The best would be to implement this on the client side, but we're already in discussions about if/how we keep the current D3-based previewer (in case there's a better one out in the wild :) )
In cases where the delimiter is wrongly detected or possibly, the rows are too big, the previewer tries to fetch too much data from the file, which of course is terrible if someone is on a mobile data connection. To solve this a (configurable) data limit has to be applied to the JavaScript that fetches the initial rows from the CSV file.
See for example the previewer trying to work with a 1.2GB CSV file: https://zenodo.org/record/3731542
The text was updated successfully, but these errors were encountered: