open-feature / open-feature/spec
NOT_READY event?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 58
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 2
Description
There are a couple of cases when client's underlying provider may change its status to NOT_READY:
- SDK is shutdown
- domain provider is swapped for another provider, which is still initializing
However, there's no event to signal this.
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 reviewing the OpenFeature provider status lifecycle and the two NOT_READY cases described in the issue. Define and document the event's expected behavior for shutdown and provider swaps; the payload names no files or tests, so completion should be verified against the specification's resulting event semantics.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100