[AStaroverov]

What

When a project has no metadata columns yet, the metadata import dialog no longer shows the per-column dropdowns ("Add as a new column / Do not import"). There is nothing to fill, so every column of the file is added as a new metadata column.

Changes

• ImportMetadataDialog.vue: the column-mapping section (dropdowns and the warnings under them) is shown only when the project already has metadata columns and the mode is "Keep existing columns".
• "Import information" reads File columns: N (all N added) in this case instead of (N added, 0 filling existing, 0 skipped).
• Changeset: patch for the block and the UI package.

Note

Without existing columns, the "added under a new name" warning for duplicate headers inside the file is no longer shown; such a column is still added as name (2). Replace mode never showed it either.

Checks

• pnpm check (ui): passes
• pnpm test (ui): 82/82
• Not verified in the desktop app.

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

The metadata import dialog now hides column choices when the project has no metadata columns. The import summary says all file columns are added.

• Metadata imports add every non-sample file column when a project has no metadata.

Important touched terms; no type definitions changed:

• ImportMode: "keep" | "replace" selects whether existing metadata stays or is replaced. Column choices now appear only for "keep" when metadata already exists.
• ColumnTarget: selects whether a file column becomes new metadata, fills an existing column, or is ignored. Projects without metadata use the existing new-column defaults without showing these choices.
• MetadataColumnMapping: maps file-column indexes to ColumnTarget values. This change hides its controls for projects without metadata; the mapping logic stays unchanged.

_{Reviews (1) · Last reviewed commit: "Add every file column on metadata import..." · Reviewed by Greptile}