`drive sheets` covers cell read/write, structure (add/rename/insert/duplicate/reorder/hide/delete), formatting, data validation, and protected ranges — but several parts of the Sheets v4 surface remain untouched, and the existing typed verbs cut corners deliberately documented in the changelog. Tracking what's left:
Entirely unimplemented (no request type exists anywhere in src/drive/sheets/):
- Named ranges (add/update/delete, and reading them back via
spreadsheets.get)
- Conditional formatting rules
- Charts (embed, update, delete)
- Pivot tables
- Filter views / basic filters
- Slicers
- Developer metadata
Curated flag surfaces that stop short of the API (each a documented cut, not a bug):
format-cells: no font family, rotation, hyperlink display, padding, or text directionset-data-validation: only 4 condition types (--one-of-list/--number-between/--checkbox/--custom-formula) of Sheets' several dozenupdate-borders: no inner-grid-line fields
Adjacent, not Sheets proper but same gap shape:
- No Slides read/write surface at all
drive docs read: document body only — headers, footers, footnotes are unread
Explicitly out of scope for this issue: a raw --requests file.json batchUpdate passthrough. ADR-0061/ADR-0075 rejected that path on purpose — it would let one call bypass the per-operation permission gate and make --dry-run unable to describe the real effect. Closing the gaps above should follow the existing pattern: one typed subcommand (or flag) per capability, gated the same way the rest of the surface is.
`drive sheets` covers cell read/write, structure (add/rename/insert/duplicate/reorder/hide/delete), formatting, data validation, and protected ranges — but several parts of the Sheets v4 surface remain untouched, and the existing typed verbs cut corners deliberately documented in the changelog. Tracking what's left:
Entirely unimplemented (no request type exists anywhere in
src/drive/sheets/):spreadsheets.get)Curated flag surfaces that stop short of the API (each a documented cut, not a bug):
format-cells: no font family, rotation, hyperlink display, padding, or text directionset-data-validation: only 4 condition types (--one-of-list/--number-between/--checkbox/--custom-formula) of Sheets' several dozenupdate-borders: no inner-grid-line fieldsAdjacent, not Sheets proper but same gap shape:
drive docs read: document body only — headers, footers, footnotes are unreadExplicitly out of scope for this issue: a raw
--requests file.jsonbatchUpdatepassthrough. ADR-0061/ADR-0075 rejected that path on purpose — it would let one call bypass the per-operation permission gate and make--dry-rununable to describe the real effect. Closing the gaps above should follow the existing pattern: one typed subcommand (or flag) per capability, gated the same way the rest of the surface is.