-
### Current Behavior
If you try to build something using the `@nrwl/js:tsc` executor that depends on some other packages in the repository, it works as long as the target that is running it is name…
-
As an end-user considering adopting or advocating for OpenFeature, I need to have confidence that my tooling vendors are "available" in OpenFeature.
As a tooling vendor, I want to promote that it's…
-
# Add ConfigCat provider
## Reasoning
I want to add an OpenFeature provider for ConfigCat.
This would be valuable because we are using that system in our projects and would like to be able to …
-
Add named client support to the JS SDK based on the recent update to the spec: https://github.com/open-feature/spec/commit/4cf8229d23a88feeaadf8b066e5d3662b94ff262
This feature has already been imp…
-
### Observed behavior
I follow tutorial https://docs.openfeature.dev/docs/tutorials/getting-started/go
and when I change value in `flags.flagd.json` by tutorial.
```json
{
"flags": {
…
-
### Change in the documentation
- [x] Identify the doc tooling that should be used
- [x] Publish docs to Netlify after a successful merge to main
- [ ] Create issues to expand on areas in the docs …
-
### Requirements
I think the content on this page: https://docs.openfeature.dev/
should actually just get put on openfeature.dev directly.
Going to docs.openfeature.dev should drop us into http…
-
To align with the contents of the readme and python standard practices the requirements.txt file should not be empty. It should match the dev in the main branch. If dev is different it should be in a …
-
### Is your feature request related to a problem? Please describe.
[We](http://github.com/utilitywarehouse) are migrating to Open Feature across our clients & want a ConfigCat provider.
### Desc…
-
### Change in the documentation
Add this link: `https://killercoda.com/open-feature/scenario/five-minutes-to-feature-flags` to this page: `https://openfeature.dev/docs/tutorials/five-minutes-to-featu…