open-feature / open-feature/cpp-sdk
Spec v0.9.0 compliance
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6
- Forks
- 2
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 5
Description
Tracks spec v0.9.0 compliance. Early stage; hook lifecycle + events are prerequisites for most items.
-
#117 #77 #78 #122 Wire hooks into evaluation
-
#92 Pin gherkin harness to v0.9.0
-
Events subsystem
-
Tracking
-
Logging hook
-
Hook data (integrate existing type)
-
Evaluation details in
finallyhook -
Telemetry utility (Appendix D)
-
Isolated API instances
-
Domain in provider init
-
Provider state via events
-
Multi-provider (optional)
-
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 by reading the linked Spec v0.9.0 release and the prerequisite issues #117, #77, #78, and #122, since no files or tests are named. The scope spans hooks, events, telemetry, provider lifecycle, and optional multi-provider support; done means the applicable checklist items comply with the referenced specification sections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100