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

sails-hook-stateflow

v1.1.4

Published

State framework for SailsJS

Downloads

50

Readme

States

state, just a unique string that is written to a specific field in the model,

Recommendation: Name the site so that the name answers the question: what is happening with your object now?

Routes and rules - Routes and Navigation rules.

Routes is where it can go from this state.

Transition rules are methods that will be called before afterState() in order to identify potential transition routes. The route code is executed before the next state is validated. To stop the transition, just call throw in one of the rules.

Recommendation: do not perform actions that modify data, since the transition rule can be canceled if the transition for some reason did not take place.

Jump queue: 1.stateValidation() 2. Updates the state field in the model 3. inState() of the state you have moved to 4. afterState() of the previous state

##Validations

stateValidation() validation when entering a state

Similar to beforeValidation conditions. Throw an error to fail stateValidation function. In other cases it will pass you further, to inState function.

note: To jump to a state, all functions must return true.

inStateCallback

inStateCallback() method that will be called when entering the state

note: errors are ignored

###after state callback

afterState()

note: errors are ignored

TODO

  1. Add states by config 🗹
  2. Add/Remove states by API 🗹
  3. Add/Remove routes by API 🗹
  4. Validation beforeNext() 🗹
  5. Select next state by cutom routes 🗹
  6. List of all routes
  7. error when create model with not startState

Config


//const State = require('sails-hook-stateflow').State;
module.exports.stateflow = {
  models: {
    /** If no model defined in sails.config.stateflow, hook use Order model */

    NotOrder: {
      /** default state */
      stateField: "not_state",
      
      /** Create attribute of waterline model with required option. by default false*/
      waterlineRequired: true

      /** Generate init states */
      states: {
        alpha: ["beta"],
        beta: ["gamma"],
        gama: ["zeta"],
        zeta: ["alpha"],
      },
    },

    Order: {
      /** if you set statrtState you must make waterlineRequired = false */
      startState: "ONE",
      states: {
        ONE: ["TWO"],
        TWO: ["THREE", "FOUR"],
        TRHEE: ["ONE", "FOUR"],
        FOUR:[],
      },
    },
  },
};

  1. after creation, you need to do next to start the first state, if created immediately with the state, then it gets that inState will never be called.

This module works with dark-sails patches

Run only by 'stateflow:runHook' event

If you want stateflow to run only after stateflow:runHook event, use runOnlyByEvent flag in config. Example:

module.exports.stateflow = {
    models: ...
    runOnlyByEvent
}