npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sourceloop/feature-toggle

v2.1.3

Published

Package for feature toggle.

Downloads

1,168

Readme

@sourceloop/feature-toggle

LoopBack

A simple loopback-next extension for checking the disabled features. Here a new decorator is introduced it has a simplistic approach to check if a particular feature is allowed or not to that user.

Working and Flow

This extension provides a method level decorator @featureFlag that takes the name of the feature that needs to be checked as metadata and verifies if that particular feature is allowed or not. What it expects is that a list of disabled features is saved for the current user of the type IAuthUserWithDisabledFeat and compares that with the one passed in the metadata of the decorator. The metadata also accepts an optional options that has a handler name parameter. If that handler name is provided that using an extendion point HandlerService appropriate handler is called. All the handlers must implement FeatureHandler interface.

Only feature check

 @featureFlag({featureKey: 'feature_key'})

If you want to skip the check:

@featureFlag({featureKey: '*'})

Multiple feature check with operator

@featureFlag({
    featureKey: ['feature_key1', 'feature_key2'],
    options: {
      operator: 'AND' | 'OR'
    },
  })

Feature Check plus handler call

@featureFlag({
    featureKey: 'feature_key',
    options: {
      handler: 'handler_name',
    },
  })

This particular handler_name will be matched with the one in handler

@injectable(asFeatureHandler)
export class MyHandler implements FeatureHandler {
  handlerName = 'handler_name';

  handle(): void {
    // your logic here
  }
}

A good practice is to keep all feature strings in a separate enum file like this.

export enum FEATUREKEY {
  CALENDAR = '1',
  CHAT = '2',
  CONTRACT = '3',
}

Install

npm install @sourceloop/feature-toggle

Basic Use

Setup

In order to use this component into your application follow the easy steps given below.

  • While authentication save the list of disabled features for that particular user. Like this
authUser.disabledFeatures = ['1', '3'];
  • Add the FeatureToggleComponent to your Loopback4 Application (in application.ts) where you need to check the features availability.
// import the FeatureToggleComponent
import {FeatureToggleComponent} from '@sourceloop/feature-toggle';

// add Component for FeatureToggle
this.component(FeatureToggleComponent);
  • Adding handlers to the extension points
this.add(createBindingFromClass(MyHandler));
  • Then add the decorator over all the APIs where feature needs to be checked. As shown above.

Feedback

If you've noticed a bug or have a question or have a feature request, search the issue tracker to see if someone else in the community has already created a ticket. If not, go ahead and make one! All feature requests are welcome. Implementation time may vary. Feel free to contribute the same, if you can. If you think this extension is useful, please star it. Appreciation really helps in keeping this project alive.

Contributing

Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.

Code of conduct

Code of conduct guidelines here.

License

MIT