-
I was making a [change](https://github.com/open-feature/node-sdk/pull/20) to the Node SDK to remove the provider accessor from the API (https://github.com/open-feature/spec/issues/84, https://github.c…
-
It looks like we use both in different places. Which is the official one?
-
Release checklist:
- [x] Release spec v0.2.0
- [x] Update spec badge on the org readme
- [x] Create issues in the SDK repos containing the new requirements
- [x] Java
- [x] Node
- …
-
### Requirements
The flag configuration contains a state property. This property can be either `ENABLED` or `DISABLED` according to the [schema](https://github.com/open-feature/schemas/blob/main/json…
-
### Requirements
## Overview
FlagD supports multiple options that affect how consumers interact with it. Options like what port or service provider is being used needs to be in sync with an OpenFe…
-
When coverage is disabled the process will fail because it expects the coverage folder to exist in the artifacts output.
`Unexpected error Could not find a part of the path 'REPO\artifacts-dotnet-r…
-
# Flagd Initial Scope
Flagd is intended to be a lightweight feature flag control plane that's compliant with the OpenFeature specification. It's responsible for managing feature flag configurations…
-
All of our client and server side libraries should support experience continuity and multivariate feature flags. This is the spec for functions we'd want to see:
## Client Side Spec
* A mechanis…
-
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, create…
-
Create a cert, store it in secure place that the OpenFeature team has access to.
https://docs.microsoft.com/en-us/nuget/create-packages/sign-a-package