JavaScript
1. Install and import package
npm i @pataflags/sdk-js
2. Initialize the SDK
const user = { id: 'aUserId' }
const pfclient = PFClient.initialize('YOUR_API_KEY', user);
3. Get your values
pfclient.onReady(() => {
const isEnabled = pfclient.isEnabled('myAwesomeFeature');
if (isEnabled) {
// Show the feature
} else {
// Hide the feature
}
});
You can set custom parameters to the client by creating a custom configuration object:
const options = { timeout: 500 };
const pfclient = PFClient.initialize('YOUR_API_KEY', user, options);
Parameter | Description | Default |
storage | none | |
bootRun | network | |
fallback | null | |
timeout | The number of milliseconds the SDK waits for a response from the Koople servers before returning the evaluation object from the storage or fallback. See timeout. | 2000 |
pollingInterval | Interval in seconds with which the SDK makes requests to the server to update the settings. See pollingInterval. | 0 |
Use
storage to keep your evaluation object response in the cache. When the request fails, the SDK try automatically to get the latest valid evaluation object from storage.Value | Behaviour |
none | |
session | |
persistent |
const pfclient = PFClient.initialize('YOUR_API_KEY', user, {
storage: 'persistent'
});
Value | Behaviour |
network | The default value. The SDK will boot from the server response. |
storage | The SDK will boot with the lastest stored response. Meanwhile, the request is loading in the background, and the evaluation object will be updated with the new server response. This mode allows loading the page without any delay. |
const pfclient = PFClient.initialize('YOUR_API_KEY', user, {
bootRun: 'storage'
});
Use
fallback to provide a default evaluation object for the SDK. When the request fails, and the storage is empty, the fallback will be returned. If the SDK has already initialized successfully, the fallback will not take effect.const pfclient = PFClient.initialize('YOUR_API_KEY', user, {
fallback: YOUR_EVALUATION_OBJECT
});
Alternatively, you can provide your fallback from
storage. This means that in case of failure, the last valid server configuration will be returned.The number of milliseconds the SDK waits for a response from the Koople servers before returning the evaluation object from the storage or fallback.
Timeout is more useful when combines with fallback. The minimum value
timeout is 50 milliseconds. If the value is less than 50 it will be ignored and automatically set to 50. If you want less than 50 milliseconds, then see bootRun.const pfclient = PFClient.initialize('YOUR_API_KEY', user, {
timeout: 50
});
You can configure your SDK to update the evaluation object every
pollingInterval seconds automatically. You will receive the changes in the subscription to onChanges.The minimum value is
1 second. If the value is less than 1 it will be ignored and automatically set to 1.const pfclient = PFClient.initialize('YOUR_API_KEY', user, {
pollingInterval: 60
});
pfclient.onChanges(() => {
// ...
});
The SDK will raise the ready event when the SDK is initialized.
The initialization will depend on the SDK configuration. If you have configured the
bootRun parameter as storage, the initialization will be immediate. Else it will take until the server responds.You can subscribe to the ready event before or after the SDK initialization, in both cases, the callback will be executed.
pfclient.onReady(() => {
const isEnabled = pfclient.releaseToggle('myAwesomeFeature');
if (isEnabled) {
// Show the feature
} else {
// Hide the feature
}
});
pfclient.onIdentified(() => {
// ...
});
While the ready and identified events are fired only once, changes will be fired every time the evaluation object is updated, including the times ready and identified events are fired.
Changes event can cause that, if the evaluation object changes, the page will be repainted or cause UI flickering.
In some cases, you can use changes event as a mechanism to ask the user if wants to apply changes or reload the page.
pfclient.onChanges(() => {
if (confirm('There is a more updated version of the page.' +
'Do you want to reload the page?')) {
// apply changes or reload page
}
});
The
releaseToggles method will return a map of release toggles with its settings.pfclient.releaseToggles();
The
isEnabled method will return a boolean indicating whether a release toggle is enabled or disabled.Name | Type | |
releaseToggleKey | string | required |
pfclient.isEnabled('myAwesomeFeature');
The
remoteConfigs method will return a map of remote configs with its settings.pfclient.remoteConfigs();
The valueOf method will return a value for a remote config. You can pass an optional second parameter used as a fallback if there is no value.
Name | Type | |
remoteConfigKey | string | required |
fallback | string | optional |
pfclient.valueOf('theme', 'light');
pfclient.evaluation();
The identify method provides a mechanism to update your evaluation object when the user has changed. It's the typical login scenario when a user goes from being anonymous to an authenticated user.
Changes will be listened from
onIdentified and onChanges.Name | Type | |
user | required |
client.onIdentified(() => { /* UPDATED SETTINGS */ });
client.onChanges(() => { /* UPDATED SETTINGS */ });
client.identify({ id: 'logged-user' });
The refresh method provides a mechanism to update your evaluation object manually. It is manual polling.
Changes can be listened from
onChanges.client.onChanges(() => { /* UPDATED SETTINGS */ });
client.refresh();
// TODO ...
Each request to the server will have an evaluation object as a response. Also,
fallback parameter is an evaluation object. You can retrieve the current evaluation object using evaluation method.A valid evaluation object should contain these fields:
Name | Description |
releaseToggles | Is a map of key values.
|
remoteConfigs | Is a map of key values.
|
const evaluationObject = {
releaseToggles: {
myAwesomeFeature: true,
mySuperFeature: true
},
remoteConfigs: {
theme: 'dark',
permissions: 'ADMIN'
}
};
Last modified 2yr ago