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

lore-hook-actions

v0.13.0

Published

A lore hook that generates default actions from blueprints

Downloads

11

Readme

lore-hook-actions

Purpose

Loads all user defined actions, which will override any blueprints previously created. Also binds all the actions to the Redux store, so they can be accessed like lore.actions.todo.create(...) without having to call bindActionCreators and pass in the store's dispatch method.

Iterates through all models in lore.models and creates actions for all of them.

Dependant Hooks

Depends on the redux hook being run first as it needs to bind the actions to lore.store.

Needs to be run after the actionBlueprints hook or else the blueprints will override the user defined actions.

Needed improvements

Suggestions welcome if you think of something.

Example Usage

Given a project where a custom todo.create has been declared by creating a src/actions/todo/create.js file:

src
|-actions
  |-todo
    |-create.js

This hook will find it and expose it on lore.actions.todo.create. Custom actions can take two forms, a config object that primarily exists just to expose before and after hooks and modify the ActionTypes that the blueprints emit, or a function that serves as a full replacement of the default action.

Example replacement action:

// file: src/actions/todo/create.js

module.exports = function create(params) {
  return function(dispatch) {
    const model = new lore.models.todo(params);

    model.save().done(function() {
      dispatch({
        type: ActionTypes.UPDATE_TODO,
        payload: payload(model, PayloadStates.RESOLVED)
      });
    }).fail(function(response) {
      const error = response.responseJSON;
      dispatch({
        type: ActionTypes.UPDATE_TODO,
        payload: payload(model, PayloadStates.ERROR_CREATING, error)
      });
    });

    return dispatch({
      type: ActionTypes.ADD_TODO,
      payload: payload(model, PayloadStates.CREATING)
    });
  };
};

Example blueprint modification through config

In this config object, we're modifying the default "onError" behavior to simply remove any todos that fail creation, but to log an error to the console.

// file: src/actions/todo/create.js

module.exports = {
  blueprint: 'create',

  model: lore.models.todo,

  optimistic: {
    actionType: ActionTypes.ADD_TODO,
    payloadState: PayloadStates.CREATING
  },

  onSuccess: {
    actionType: ActionTypes.UPDATE_TODO,
    payloadState: PayloadStates.RESOLVED
  },

  onError: {
    actionType: ActionTypes.REMOVE_TODO,
    payloadState: PayloadStates.ERROR_CREATING,
    beforeDispatch: function(response, args){
      lore.log.error('Oh no! The create called failed. Deleting todo.')
    }
  }
};