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

@sap/hana-tooling-feature-toggles

v1.3.0

Published

A node library for checking feature toggles. It gives you the option to create standard feature toggles and also feature toggles for Visual Studio Code commands.

Downloads

124,896

Readme

@sap/hana-tooling-feature-toggles

A node library for checking feature toggles. It gives you the option to create standard feature toggles and also feature toggles for Visual Studio Code commands.

Usage

Instantiation

Create an instance managing your feature toggles. The first parameter has to be either a JSON object or a string. The second parameter is the name of your Visual Studio Code extension (optional) if you want to enable / disable Visual Studio Code commands. The third parameter is a Visual Studio Code API object (optional). Depending on the type of your first parameter the module will a) directly use the provided feature toggles. b) check if the string is stringified JSON. c) try to read the file at the provided path.

Pure Node.js:

    // With JSON parameter.
    import FeatureToggles = require("@sap/hana-tooling-feature-toggles");
    const myFeatures = {
        "featureToggles": [
            {
                "name": "helloworld",
                "status": "released"
            }
        ]
    };
    const FeatureToggleInstance = new FeatureToggles(myFeatures);
    // With string parameter.
    import FeatureToggles = require("@sap/hana-tooling-feature-toggles");
    const FeatureToggleInstance = new FeatureToggles(__dirname + "/../features.json");
    // With stringified JSON parameter.
    import FeatureToggles = require("@sap/hana-tooling-feature-toggles");
    const myFeatures = {
        "featureToggles": [
            {
                "name": "helloworld",
                "status": "released"
            }
        ]
    };
    const featureString = JSON.stringify(myFeatures);
    const FeatureToggleInstance = new FeatureToggles(featureString);

Visual Studio Code:

    const vscode = require( 'vscode' );
    import FeatureToggles = require("@sap/hana-tooling-feature-toggles");
    const FeatureToggleInstance = new FeatureToggles(__dirname + "/../features.json", "featuretoggletest", vscode);

The structure of your JSON object / file (first parameter) should be:

{
    "featureToggles": [
        {
            "name": "helloworld",
            "status": "released"
        },
        {
            "name": "helloworlddisabled",
            "status": "dev"
        },
        {
            "name": "helloworldqa",
            "status": "candidate"
        }
    ]
}

The name is the unique identifier of your feature and the status determines whether it is in development, a candidate for release or a released feature.

API

    FeatureToggles.isFeatureEnabled("featureToggleName")

This function checks if the feature 'featureToggleName' is enabled inside your specified .json file for feature toggles:

  • If the feature is enabled (for example 'helloworld' in the code above), it will return true.
  • If the feature is disabled (for example 'helloworlddisabled' in the code above), it will call _isFeatureQaEnabled("featureToggleName") and return the internal result.
    FeatureToggles.isCommandEnabled("featureToggleName")

This function should only be used if you are developing a Visual Studio Code extension and want to set feature toggles for commands. It will work like '.isFeatureEnabled("featureToggleName")' with the difference that it will set a Visual Studio Code context variable which makes the command visible to the user.

The set Visual Studio Code context variable will be:

    "extensionName:featureToggleName"

So the package.json file of your extension should contain the following structure:

	"contributes": {
		"commands": [
			{
				"command": "extensionName.commandName",
				"title": "Hello World (enabled)"
			}
		],
		"menus": {
			"commandPalette": [
				{
					"command": "extensionName.commandName",
					"when": "extensionName:featureToggleName1"
                }
            ],
            "editor/context": [
                {
					"command": "extensionName.commandName",
					"when": "extensionName:featureToggleName2"
				}
            ]
        }
    }

License

This package is provided under the terms of the SAP Developer License Agreement.