Row index base for text files (.csv, .parquet, etc) should follow the convention for the selected kernel

[jonpeake]

I've noticed that opening text data files like .csv and .parquet in the data viewer from the files pane defaults to a 0-indexed row numbering system. In my experience, this can cause some confusion among R users who are used to working with 1-indexed row numbers. A better option may be to assign the row indexing for these files based on the active kernel (R or Python). Not sure if this is possible under the current architecture, but it would be a nice feature to have. Or at the very least a toggle to change between 0-based and 1-based row index.

[juliasilge]

Thanks for this feature request! 🙌

When you click to open a CSV, Parquet, etc in the Data Explorer, this actually does not use R or Python at all (it uses DuckDB under the hood). You could do this without any R or Python even running in your workspace. I think it's unlikely we would do work to make this UI configurable in the near term, but we can collect opinions and feedback here on this discussion about how important this is for folks.