open-feature / open-feature/js-sdk
[FEATURE] web-sdk: Access to provider status inside the provider
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 282
- Forks
- 72
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 16
Description
Requirements
With the web-sdk v1.0.0, the provider status is now managed directly by the SDK which is great, but there are some usecases when it will be interesting to have access to the provider status inside the SDK.
One of the use cases I have is being able to send a CACHED reason when the provider is STALE.
Contributor guide
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 tracing how provider status is managed in the web-sdk v1.0.0 and how provider code currently receives SDK state. Define the access behavior needed for a provider to detect STALE status and send a CACHED reason, then verify the provider-facing API and its behavior with the existing SDK tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100