open-feature / open-feature/ruby-sdk
Spec v0.9.0 compliance
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 43
- Forks
- 18
- Avg merge
- 6h 21m
- Merged PRs (30d)
- 19
Description
Tracks spec v0.9.0 compliance.
-
#297 Domain in provider init
-
Isolated API instances
-
Wire telemetry helper into eval path; verify Appendix D alignment
-
Multi-provider (optional)
-
Init + pin
specsubmodule to v0.9.0 -
Provider lifecycle event ownership (race-condition fix): add opt-in marker so providers emit their own
PROVIDER_READY/PROVIDER_ERROR; SDK derives status from the provider event stream and keeps + deprecates the legacy synthetic path; update first-party providers (spec 5.3.5, provider status 2.8, Appendix E)
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 with the v0.9.0 specification, the spec submodule update, and the linked requirements in sections 5.3.5, 2.8, Appendix D, and Appendix E. Then trace the provider lifecycle event and evaluation paths, including the first-party providers. Done means each checklist item is implemented and the SDK's behavior aligns with the referenced specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100