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

@citybrewcoffee/rule-engine

v1.1.1

Published

An engine that defines rules and combines them recursively.

Downloads

18

Readme

Tyepscript Rule Engine

This package is meant to help with processing complex rules and checking if dynamic data fits those rules.

Quickstart

You can start by creating your own rule by extending the rule object and implement an isValid() function. Here's an example:

class StringContainsRule extends Rule<string> {
  type = 'STRING_CONTAINS_RULE';

  letterToContain: string;

  constructor(letterToContain: string) {
    super();
    this.letterToContain = letterToContain;
  }

  isValid(input: string): boolean {
    return input.includes(this.letterToContain);
  }
}

Built in Rules

There are 3 rules already made by this package that can be used out of the box:

  • Rule Group: Takes in a list of rules as subrules; isValid() return the logical 'AND' or 'OR' of the rules
  • Not Rule: Takes in a rule; isValid() return the logical NOT of the rule
  • List Rule: Takes in a rule of specific type and optional parameters on how to calculate the end result; isValid() takes a list of objects and returns true if conditions are met on the list (ie all items meet certain rule, or exacly 5 items, ect)

Serializing

All rules inherit a toJson() method and toObject() method for storage in a database.

Deserializing with Rule Store

A RuleStore is an object in memory that knows how to build rules from json or plain objects. RuleStores already know how to build built-in rules (RuleGroup, ListRule, and NotRule), and you can "teach" it how to build your custom rules by feeding it a type string and build function, like so:

const store = new RuleStore([
  {
    type: 'STRING_CONTAINS_RULE',
    build: (json) => new StringContainsRule(json.letterToContain as string),
  },
]);

Rule Return Type

While rules will return boolean by default, you can add a second optional generics paramters to rules to make them return something else, like a number. Here's an example.

class StringLengthRule extends Rule<string, number> {
  type = 'STRING_LENGTH_RULE';
  isValid(input: string): number {
    return input.length;
  }
}

Note that if your rule doesn't return booleans, it can not be used with the built-in RuleGroup, NotRule, or ListRule.