gog sheets batch-update --requests-json
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.4k
- Forks
- 697
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 89
Description
I know this was closed in #1103, but I'd like to make a proper pitch. batch-update is better and different vs api call:
batch-updatehas a narrow security scopebatch-updatefacilitates editing transactions, and acts as a single API request for rate limitingbatch-updateworks with safe buildsapi callopens up a can of worms and has to download the entire schema for discovery (slooowwwww)
batch-update is the best, let's do more of that! api call is for desperate agents, no need to go there in this case. I won't bring it up again in either case, just marshaling my arguments here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing gog sheets batch-update and api call entry points, along with the discussion in issue #1103. No files or tests are named, so first establish the intended --requests-json scope and acceptance criteria. Done means the proposed batch-update behavior is clearly defined and supported by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100