Caslin Feature

An application feature management JS framework to support multi-environments, multi-roles, multi-scenarios

This framework is transformed from Casl and is motivated by the actual needs (multi-environments feature management). It is used to manage the features and abilities of your application in multiple environments. The application features can be tailored and joined according to the environments and roles.

Special thanks to Casl, without Casl there is no current Caslin.

English | 中文

Features of Caslin

• Able to customize features in multiple environments
• Centralized feature management for easy viewing, definition, and changes
• Feature definition meets the free combination of functions, roles, and environments
• Feature definition and feature implementation decoupling, flexible change of feature definition or feature implementation
• Transformed from Casl, the underlying API logic is simple and clear, while providing a friendly, easy-to-use React utility

Difference between Casl

• Source code written by TypeScript
• Introduce the concept of the "environment" to solve the problem of "same function, different environment" that Casl does not focus
• Add environment-related APIs and React HOC components

Installation

npm install @caslin/feature --save

Getting start

Principle: Each feature rule corresponds to a basic semantic：At <environment> can <do> <something>.

1. Definite feature

Generate a feature instance by defining multiple rules.

import { FeatureBuilder } from '@caslin/feature';

const feature = FeatureBuilder.define((can, cannot, at) => {
  at('all').can('read', 'Article');
  at('featEnv1').can('create', 'Article');
  at('featEnv2').cannot('delete', 'Article');
  can('read', 'Comment'); // Alias of `at('all').can('read', 'Comment');`
});

2. Check ability

Use the feature instance to check if you have the corresponding ability.

feature.at('featEnv1').can('create', 'Article'); // true
feature.at('featEnv2').cannot('delete', 'Article'); // true
feature.at('featEnv1').cannot('delete', 'Article'); // true
feature.at('featEnv2').cannot(['delete', 'create'], 'Article'); // true
feature.at('featEnv2').can('read', 'Article'); // true, because "all" env could "read"
feature.can('read', 'Comment'); // true. Alias of `feature.at('all').can('read', 'Comment');`

3. Set the default environment, then check the environment (optional)

Set the current default environment and check if the passed environment matches the default environment.

feature.setEnv('featEnv1'); // set current environment as "featEnv1"，could be reset by `feature.resetEnv()`

// Check feature
feature.can('read', 'Article'); // true, same as `feature.at('featEnv1').can('read', 'Article')`
feature.can('manage', 'Article'); // true
feature.cannot('delete', 'Article'); // true

// Check environment
feature.env.is('featEnv1'); // true，current environment is "featEnv1"
feature.env.not('featEnv2'); // true，current environment is not "featEnv2"
feature.env.in(['featEnv2', 'featEnv3']); // false，current environment isn't been included
feature.env.notIn(['featEnv2', 'featEnv3']); // true，current environment isn't been included

API

FeatureBuilder

• FeatureBuilder.define(definer: Definer)

Receive a parameter of type Definer to generate a feature instance. The type is { (definer: Definer): Feature }.

Definer

The function that defines the rule, of type { (can, cannot, at): Promise<any> | void }, the basic usage of defining a rule is at('environment').can('read', 'Article' ).

You can omit at() to indicate that this rule applies to all environments, such as can('read', 'Article'), which is equivalent to at('all').can('read', 'Article') .

Feature

Suppose there is already a feature for the instance of Feature.

• feature.at('env').can('action', 'subject')

Check if it is able to do action/actions on a subject at arbitrary environment, returns true if yes, otherwise returns false.

• feature.at('env').cannot('action', 'subject')

Check if it is unable to do action/actions on a subject at arbitrary environment, returns true if yes, otherwise returns false.

• feature.setEnv('env')

Set the current default environment.

• feature.resetEnv()

Reset the current default environment.

• feature.env.value

The value of current default environment.

• feature.env.is('env')

Check that the current default environment is "env", return true if it is, or false otherwise.

• feature.env.not('env')

Check that the current default environment is "env", return true if it isn't, or false otherwise.

• feature.env.in(['env1', 'env2'])

Check that the current default environment is included in env1, env2 and return true if it contains, otherwise return false.

• feature.env.notIn(['env1', 'env2'])

Verify that the current default environment is included in env1, env2 and return true if it is not, otherwise return false.

• feature.env.matchPick({ env1: 'value1', env2: 'value2' })

Pick the key-value pair whose key matches current environment, return the value of mathced key-value pair.

• feature.rules

In general case, you don't need to use it. It is underlying used by the framework and represents the basic definition of the "feature". The type is Rule[].

• feature.update(rules)

In general case, you don't need to use it. Update the feature with the new rule. The parameter is a Rule array: Rule[].

There are fewer cases to update the rules. Calling feature.setEnv('env') or feature.resetEnv() to set the current default environment could solve the problem at most time.

• feature.on('event', handler)

In general case, you don't need to use it. Used to listen for events emitted by feature, such as feature.update(), feature.setEnv(), feature.resetEnv(), each time the updated event is emitted, which can be listened to.

The return value of feature.on() is a unsubsribe() function, which can cancel the listener of the handler after calling.

• feature.emit('event', payload)

In general case, you don't need to use it. Emits the specified event, passes the corresponding payload, and executes all the listeners corresponding to the specified event. The input parameter of each listener function is payload.

Rule

In general case, you don't need to use it. Underlying used by the framework to represent the basic definition of the property. A set of rules could be get via feature.rules.

License

MIT License