You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/browser-sdk/README.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -176,6 +176,8 @@ generate a `check` event, contrary to the `isEnabled` property on the object ret
176
176
177
177
### Remote config (beta)
178
178
179
+
Remote config is a dynamic and flexible approach to configuring feature behavior outside of your app – without needing to re-deploy it.
180
+
179
181
Similar to `isEnabled`, each feature has a `config` property. This configuration is managed from within Bucket.
180
182
It is managed similar to the way access to features is managed, but instead of the binary `isEnabled` you can have
181
183
multiple configuration values which are given to different user/companies.
@@ -194,10 +196,7 @@ const features = bucketClient.getFeatures();
194
196
// }
195
197
```
196
198
197
-
The `key` is always present while the `payload` is a optional JSON value for arbitrary configuration needs.
198
-
If feature has no configuration or, no configuration value was matched against the context, the `config` object
199
-
will be empty, thus, `key` will be `undefined`. Make sure to check against this case when trying to use the
200
-
configuration in your application.
199
+
`key` is mandatory for a config, but if a feature has no config or no config value was matched against the context, the `key` will be `undefined`. Make sure to check against this case when trying to use the configuration in your application. `payload` is an optional JSON value for arbitrary configuration needs.
201
200
202
201
Just as `isEnabled`, accessing `config` on the object returned by `getFeatures` does not automatically
203
202
generate a `check` event, contrary to the `config` property on the object returned by `getFeature`.
@@ -321,6 +320,13 @@ The two cookies are:
321
320
-`bucket-prompt-${userId}`: store the last automated feedback prompt message ID received to avoid repeating surveys
322
321
-`bucket-token-${userId}`: caching a token used to connect to Bucket's live messaging infrastructure that is used to deliver automated feedback surveys in real time.
323
322
323
+
### Upgrading to 3.0 from 2.x
324
+
325
+
Breaking changes:
326
+
327
+
-`client.onFeaturesUpdated()` is now replaced by [event listeners](#event-listeners)
328
+
- Arguments to the `BucketClient` constructor which were previously under `featureOptions` are now supplied directly in the root.
329
+
324
330
### TypeScript
325
331
326
332
Types are bundled together with the library and exposed automatically when importing through a package manager.
0 commit comments