mirror of https://github.com/open-feature/spec.git
65728e6975
This PR: * stabilizes evaluation API * stabilizes providers * hardens hooks, events and context * hardens all "static context" (client-side) points This is a pretty substantial step. `stable` means that we have no more leeway at all in SDKs - **any breaking changes to the parts of the SDK implementing stable APIs means a new major version of the SDK is required, without exception**. I've also opted to "harden" the `static context paradigm` since we have numerous client implementations in the wild, in particular React and Angular, but also Android. There could still be breaking changes here but the bar is higher. I think this is how we're acting already with regards to these APIs, in all honesty. I did not promote the [context propagation](https://openfeature.dev/specification/sections/evaluation-context#33-context-propagation) sub-section, or the new tracking section - these are _relatively_ new, though I'm open to opinions on hardening these further. Potential blockers: - https://github.com/open-feature/go-sdk/issues/389 - https://github.com/open-feature/spec/issues/270 Signed-off-by: Todd Baert <todd.baert@dynatrace.com> |
||
|---|---|---|
| .. | ||
| 01-flag-evaluation.md | ||
| 02-providers.md | ||
| 03-evaluation-context.md | ||
| 04-hooks.md | ||
| 05-events.md | ||
| 06-tracking.md | ||
| _category_.json | ||