Repository navigation
feat(sheets): add native range reads, cell edits and generated API coverage - #105
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drive previously imported native Sheets through XLSX for local reading/search but could not inspect or edit live cell ranges. Add profile-scoped sheets info/show/update/add/clear commands, Google's pinned official Sheets SDK and all 17 operations from a verified committed Sheets v4 Discovery snapshot (85 generated operations total).
Updates require a concrete tab/cell rectangle and values that fit it; supplied rows are limited to 10,000 cells. Strings are literals by default, while formula/locale interpretation is explicit. Append reports Google's actual inserted range, clears preserve formatting, writes reuse OAuth/policy guards and uncertain outcomes are not retried. Repeated parameters are normalized for SDK calls without allowing nested authentication/transport overrides. Existing Drive grants cover the API; enabling Sheets API is a separate project setup step.
Update native recipes, installation/API setup, source overview, generated references and CLI/MCP snapshots. Reuse canonical info/show/update/add/clear verbs. Existing lint baseline is unchanged; six dated domain exceptions await adoption of the shared vocabulary merged in cli-base#178.
Validation: 257 tests, 90.13% line coverage, 10 CLI/MCP contracts, five prior-store upgrade cases, typechecking, generation freshness, lint, Markdown, leak checks and Node/Bun installed-package smoke. All PR checks passed before merge; full main validation passed: https://github.com/WireCatLabs/drive-cli/actions/runs/38986029510. External executable evidence: https://github.com/WireCatLabs/cli-testing/tree/main/performance/documents/drive-sheets — seven checks across 17 guarded CLI invocations, with candidate source/module hashes.
No live Google request or write was performed. Shared-project Sheets API enablement and dedicated synthetic spreadsheet readback remain launch checks; this PR does not establish Google verification or npm availability.