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
{{ message }}
Repository navigation
Feature request: Global default for “Hide First N Rows” #99
Please add a global or workspace-level setting that controls the default value for Hide First N Rows.
Currently, the hidden-row count is stored per file. Users working with many CSV files that share the same structure must run CSV: Hide First N Rows and enter the value for every new file.
Proposed setting
"csv.defaultIgnoreRows": 0
The setting could default to 0 to preserve current behavior. A per-file value should override the global or workspace default.
Use case
Oracle Integration Cloud lookup CSV files contain a five-column metadata row before the actual table header. I need to hide the first row in every lookup file so the second row is displayed as the spreadsheet header.
A workspace-level value of 1 would make editing large collections of these files much easier while preserving the metadata row.
The Oracle lookup example makes the need very clear. Thank you for explaining it so thoughtfully. #118 proposes a shared default while keeping per-file exceptions and preserving the metadata. I appreciate your patience; you shouldn’t have to repeat that setup for every file.
@boerbk82, thank you for explaining the Oracle lookup workflow so clearly. CSV 1.4.2 adds csv.defaultIgnoreRows at user or workspace scope; per-file overrides still take precedence, and the metadata stays in the file. I’m sorry you had to repeat that setup before. If you have time, an honest review would mean a lot. Thank you for the thoughtful suggestion.
Activity
jonaraphael commentedon Oct 17, 2026
The Oracle lookup example makes the need very clear. Thank you for explaining it so thoughtfully. #118 proposes a shared default while keeping per-file exceptions and preserving the metadata. I appreciate your patience; you shouldn’t have to repeat that setup for every file.
jonaraphael commentedon Oct 18, 2026
@boerbk82, thank you for explaining the Oracle lookup workflow so clearly. CSV 1.4.2 adds csv.defaultIgnoreRows at user or workspace scope; per-file overrides still take precedence, and the metadata stays in the file. I’m sorry you had to repeat that setup before. If you have time, an honest review would mean a lot. Thank you for the thoughtful suggestion.