spec
spec copied to clipboard
open-feature
OpenFeature specification
This is in reference to the hooks evaluation order in [**Requirement 4.4.2**](https://docs.openfeature.dev/docs/specification/sections/hooks#requirement-442). This reads: > Hooks **MUST** be evaluated in the following order: > > - before: API, Client, Invocation,...
They look really similar in the spec (types.md especially). Maybe say what the difference is?
For providers which support changing their provider status at runtime the automatic events introduce additional complexity. The provider needs to defer its handling of the status until after the automatic...
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [markdownlint-cli](https://redirect.github.com/igorshubovych/markdownlint-cli) | [`^0.39.0` -> `^0.42.0`](https://renovatebot.com/diffs/npm/markdownlint-cli/0.39.0/0.42.0) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/)...
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "renovate[bot] avatar"){kind=avatar}
## Overview A **multi provider** acts as a unified abstraction layer, allowing developers to consolidate feature flag access through a single API. With a multi provider, developers can simultaneously support...
Building off of #254, I've started to put together a script to pull together the differences the SDKs have. In working on parsing the different repositories, I noticed that some...
See #254 . We should get that auto-publishing for easy `docker run ghcr.io/...` usage.
This PR is a first pass at a relatively simple tracking API. The main purpose is to close what is more or less the last gap between the OpenFeature API...
As discussed in recent meetings, we've had complaints about this from multiple sources. This PR adds a stipulation that no logging is done by the SDK during flag evaluation. It...
Minor clarifications to the in-memory provider, especially around `flags changed` which at the moment is not consistently implemented.