Quota Google API Calls On a per-User Basis
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Description
See documentation here: https://support.google.com/googleapi/answer/7035610?hl=en
This should be investigated, and applied to all calls to google's APIs by adding a quotaUser=user_id query parameter.
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
No files, tests, or entry points are named. Read the linked Google quota documentation, then locate every Google API call in the repository and determine how user IDs are available at each call site. Done means all Google API calls include a per-user quotaUser query parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100