About

Deno SDK for working with Switcher-API. https://github.com/switcherapi/switcher-api

• Flexible and robust functions that will keep your code clean and maintainable.
• Able to work offline using a snapshot file downloaded from your remote Switcher-API Domain.
• Silent mode is a hybrid configuration that automatically enables a contingent sub-process in case of any connectivity issue.
• Built-in mock implementation for clear and easy implementation of automated testing.
• Easy to setup. Switcher Context is responsible to manage all the complexity between your application and API.

Usage

Module initialization

The context properties stores all information regarding connectivity.

import { Switcher } from "https://deno.land/x/switcher4deno@v1.0.0/mod.ts";

const apiKey = '[API_KEY]';
const environment = 'default';
const domain = 'My Domain';
const component = 'MyApp';
const url = 'https://switcher-api.herokuapp.com';

• apiKey: Switcher-API key generated to your component.
• environment: (optional) Environment name. Production environment is named as 'default'.
• domain: Domain name.
• component: Application name.
• url: (optional) Swither-API endpoint.

Options

You can also activate features such as offline and silent mode:

const offline = true;
const logger = true;
const snapshotLocation = './snapshot/';
const silentMode = true;
const retryAfter = '5m';

Switcher.buildContext({ url, apiKey, domain, component, environment }, {
    offline, logger, snapshotLocation, silentMode, retryAfter
});

const switcher = Switcher.factory();

• offline: If activated, the client will only fetch the configuration inside your snapshot file. The default value is 'false'.
• logger: If activated, it is possible to retrieve the last results from a given Switcher key using Switcher.getLogger('KEY')
• snapshotLocation: Location of snapshot files. The default value is './snapshot/'.
• silentMode: If activated, all connectivity issues will be ignored and the client will automatically fetch the configuration into your snapshot file.
• retryAfter : Time given to the module to re-establish connectivity with the API - e.g. 5s (s: seconds - m: minutes - h: hours).

Executing

There are a few different ways to call the API using the JavaScript module. Here are some examples:

1. No parameters Invoking the API can be done by instantiating the switcher and calling isItOn passing its key as a parameter.

const switcher = Switcher.factory();
await switcher.isItOn('FEATURE01');

1. Promise Most functions were implemented using async operations. Here it is a differnet way to execute the criteria:

switcher.isItOn('KEY')
    .then(result => console.log('Result:', result))
    .catch(error => console.log(error));

1. Strategy validation - preparing input Loading information into the switcher can be made by using prepare, in case you want to include input from a different place of your code. Otherwise, it is also possible to include everything in the same call.

import { checkValue, checkNetwork } from "https://deno.land/x/switcher4deno@v1.0.0/mod.ts";

switcher.prepare('FEATURE01', [checkValue('USER_1')];
switcher.isItOn();

1. Strategy validation - all-in-one execution All-in-one method is fast and include everything you need to execute a complex call to the API.

await switcher.isItOn('FEATURE01', [
    checkValue('User 1'),
    checkNetwork('192.168.0.1')
]);

1. Throttle Throttling is useful when placing Feature Flags at critical code blocks require zero-latency without having to switch to offline. API calls will happen asynchronously and the result returned is based on the last API response.

const switcher = Switcher.factory();
await switcher
    .throttle(1000)
    .isItOn('FEATURE01');

Built-in mock feature

You can also bypass your switcher configuration by invoking 'Switcher.assume'. This is perfect for your test code where you want to test both scenarios when the switcher is true and false.

Switcher.assume('FEATURE01').true();
switcher.isItOn('FEATURE01'); // true

Switcher.forget('FEATURE01');
switcher.isItOn('FEATURE01'); // Now, it's going to return the result retrieved from the API or the Snaopshot file

Enabling Test Mode You may want to enable this feature while using Switcher Client with automated testing. It prevents the Switcher Client from locking snapshot files even after the test execution.

To enable this feature, it is recommended to place the following on your test setup files:

Switcher.setTestEnabled();

Smoke Test Validate Switcher Keys on your testing pipelines before deploying a change. Switcher Keys may not be configured correctly and can cause your code to have undesired results.

This feature will validate using the context provided to check if everything is up and running. In case something is missing, this operation will throw an exception pointing out which Switcher Keys are not configured.

Switcher.checkSwitchers(['FEATURE01', 'FEATURE02'])

Loading Snapshot from the API

This step is optional if you want to load a copy of the configuration that can be used to eliminate latency when offline mode is activated.
Activate watchSnapshot optionally passing true in the arguments.

Switcher.loadSnapshot();

Watch for Snapshot file changes

Activate and monitor snapshot changes using this feature. Optionally, you can implement any action based on the callback response.

Switcher.watchSnapshot(
    () =>  console.log('In-memory snapshot updated'), 
    (err: any) => console.log(err));

Snapshot version check

For convenience, an implementation of a domain version checker is available if you have external processes that manage snapshot files.

Switcher.checkSnapshot();