lsst-epo / lsst-epo/weather-client-function
Refactor to avoid vendor lock-in
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
After discovering limits on the free tier of Meteoblue, consider refactoring the codebase to more readily use other weather API endpoints like open-meteo.
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 mapping how the TypeScript Google Cloud Function currently calls Meteoblue and where weather API endpoints are selected. Compare the existing integration with Open-Meteo, then define completion as allowing another weather provider to be used without being tied to Meteoblue's free tier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend, cloud
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100