Geolocation not always using custom API keys?
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
It looks like the Geolocation service doesn't always use the user's custom API keys
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 locating the Geolocation service entry point and tracing how user-provided API keys are selected for each request. Reproduce a case where a custom key is ignored, then verify that configured keys are consistently used in all relevant requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100