neondatabase / neondatabase/serverless
Allow users to override `fetchFunction` and `fetchEndpoint` per instance.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 548
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
My company has a use case where we need to hit two different fetchEndpoint's in the same app but currently we can only configure on a global level. It would be nice to be able to configure on per-instance level.
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 global fetchFunction and fetchEndpoint configuration and the client or instance entry points that consume them. Check whether existing tests cover configuration scope; done means separate instances can use different endpoints and fetch functions without changing the global configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100