@openfeature/flagd-provider 0.13.1 → 0.13.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -6
- package/index.cjs.js +1800 -1735
- package/index.esm.d.ts +1 -0
- package/index.esm.js +1800 -1733
- package/package.json +11 -10
- package/src/lib/flagd-provider.d.ts +2 -6
- package/src/lib/service/in-process/file/file-fetch.d.ts +1 -1
- package/src/lib/service/in-process/grpc/grpc-fetch.d.ts +1 -1
- package/src/lib/service/in-process/in-process-service.d.ts +2 -6
- package/src/proto/ts/flagd/evaluation/v1/evaluation.d.ts +18 -14
- package/src/proto/ts/flagd/sync/v1/sync.d.ts +6 -6
- package/src/proto/ts/schema/v1/schema.d.ts +17 -14
- package/src/proto/ts/sync/v1/sync_service.d.ts +7 -4
- package/src/e2e/constants.d.ts +0 -4
- package/src/e2e/jest.config.d.ts +0 -11
- package/src/e2e/setup-in-process-provider.d.ts +0 -1
- package/src/e2e/setup-rpc-provider.d.ts +0 -1
package/README.md
CHANGED
|
@@ -61,7 +61,7 @@ In the above example, the provider expects flagd to be available at `localhost:8
|
|
|
61
61
|
|
|
62
62
|
Alternatively, you can use socket paths to connect to flagd.
|
|
63
63
|
|
|
64
|
-
```
|
|
64
|
+
```ts
|
|
65
65
|
OpenFeature.setProvider(new FlagdProvider({
|
|
66
66
|
socketPath: "/tmp/flagd.socks",
|
|
67
67
|
}))
|
|
@@ -72,7 +72,7 @@ Alternatively, you can use socket paths to connect to flagd.
|
|
|
72
72
|
This mode performs flag evaluations locally (in-process).
|
|
73
73
|
Flag configurations for evaluation are obtained via gRPC protocol using [sync protobuf schema](https://buf.build/open-feature/flagd/file/main:sync/v1/sync_service.proto) service definition.
|
|
74
74
|
|
|
75
|
-
```
|
|
75
|
+
```ts
|
|
76
76
|
OpenFeature.setProvider(new FlagdProvider({
|
|
77
77
|
resolverType: 'in-process',
|
|
78
78
|
}))
|
|
@@ -83,7 +83,7 @@ In the above example, the provider expects a flag sync service implementation to
|
|
|
83
83
|
In-process resolver can also work in an offline mode.
|
|
84
84
|
To enable this mode, you should provide a valid flag configuration file with the option `offlineFlagSourcePath`.
|
|
85
85
|
|
|
86
|
-
```
|
|
86
|
+
```ts
|
|
87
87
|
OpenFeature.setProvider(new FlagdProvider({
|
|
88
88
|
resolverType: 'in-process',
|
|
89
89
|
offlineFlagSourcePath: './flags.json',
|
|
@@ -107,9 +107,8 @@ For general information on events, see the [official documentation](https://open
|
|
|
107
107
|
|
|
108
108
|
### Flag Metadata
|
|
109
109
|
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
| `scope` | string | "selector" set for the associated source in flagd |
|
|
110
|
+
[Flag metadata](https://flagd.dev/reference/flag-definitions/#metadata) is a set of key-value pairs that can be associated with a flag.
|
|
111
|
+
The values come from the flag definition in flagd.
|
|
113
112
|
|
|
114
113
|
## Building
|
|
115
114
|
|