spec
spec copied to clipboard
open-feature
OpenFeature specification
[Requirement 3.2.2](https://github.com/open-feature/spec/blob/main/specification/sections/03-evaluation-context.md#requirement-322) should included the before hook. `API (global) -> client -> invocation -> before hooks` An explanation of why the before hook has the highest priority should be included...
## Overview We need to start defining our goals for beta, now that the alpha spec has been officially released. The beta version of the spec should include necessary clarifications,...
### Summary Evaluation context may be used to conditionally control the value returned from a flag evaluation. You could, for example, enable a feature for all users with a...
The specification doesn't appear to define a way to cleanly dispose of provider instances. Some provider implementations which uses SDKs of the vendor and these SDKs might have event listeners,...
### Problem The global singleton used in OpenFeature provides a number of benefits. However, it may introduce some challenges in the future. For example, if a library is using an...
So I'm writing a test case for 2.8. I'm not entirely clear exactly what we're trying to accomplish with it. So, ProviderEvaluation already has a mechanism for providing an error...
OpenTelemetry has a concept of [semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions). This is a form of metadata that can be applied to a span. The attribute names should comply with [their spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/attribute-naming.md). Here's an...
See the project roadmap [here](https://github.com/orgs/open-feature/projects/1)
See https://github.com/open-feature/spec/issues/141 for context.
