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

@theweirdscience/casey

v1.0.1

Published

A javascript functional approach to switch and if-else statements

Downloads

5

Readme

Build Status Coverage Status

casey

A javascript functional approach to switch and if-else statements

Installation

npm install --save @theweirdscience/casey
# or
yarn add @theweirdscience/casey

Usage

You can always start by importing the module

import casey from "@theweirdscience/casey";

Simple usage allows you to provide direct mappings from a condition value to a desired resulting value. An optional default may be provided for when there is no explicit match using strict === comparison.

casey
  .case(1, "one")
  .case(2, "two")
  .case(3, "three")
  .default("not found")
  .match(2); // "two"

A slightly more advanced approach is to provide the custom matching functions and corresponding value generating functions. This can be useful when the conditions require more than a simple strict comparison or the values are resource/processor intensive to create. When a function is provided for the value it will automatically be called and the resulting value returned by match. Comparison functions may return any value to be checked for truthiness but a boolean value is recommended for transparency.

casey
  .case(v => v === 1, () => "one")
  .case(v => v === 2, () => "two")
  .case(v => v === 3, () => "three")
  .default(() => "not found")
  .match(3); // "three"

In some less frequent cases you may wish to predetermine the desired result by providing a boolean value for the condition. In this form the same result will always be returned by match essentially overriding the provided default.

const a = 5;
casey
  .case(a === 1, "one")
  .case(a === 2, "two")
  .case(a === 3, "three")
  .case(true, "other number")
  .default("not found")
  .match(); // "other number"

You can also add your cases in batches using the map function. Casey looks for the first possible match so duplicate conditions, though possible, will always result in the first possible match. map may be called multiple times to add more cases in batches.

casey.map([[1, "one"], [2, "two"], [3, "three"]]).match(3); // "three"

In all scenarios you can mix the types of the conditions and the value as you please. They do not need to all be the same though the resulting code may make your eyes bleed.

Another advantage to using casey is the ability to provide the match function directly to an Array.map() function.

const translate = casey
  .case(1, "one")
  .case(2, "two")
  .case(3, "three")
  .default("other");
[1, 2, 3, 4].map(translate.match); // ["one","two","three","other"]

Testing

npm test

Rationale

With functional programming becoming more and more prevalent the traditional if, elseif, else way of development starts to feel clunky and unnecessary.

const value = 3;
let result = "";
if (value === 1) {
  result = "one";
} else if (value === 2) {
  result = "two";
} else if (value === 3) {
  result = "three";
} else {
  result = "other";
}
result; // "three"

is the same as

const value = 3;
casey
  .case(1, "one")
  .case(2, "two")
  .case(3, "three")
  .default("other")
  .match(value); // "three"