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

redux-helper-decorator

v0.0.2

Published

### Description This library is created for a specific behavior. This might not be fit or some functionalities might not be fit to other behaviour.

Downloads

2

Readme

redux-helper-decorator

Description

This library is created for a specific behavior. This might not be fit or some functionalities might not be fit to other behaviour.

Methods available:

  1. getReducers
  2. getSocketResponseHandlerList

getReducers -> Return all reducers in classes decorated with @reducer. This method will return a JSON object. Think of the JSON passed to createStore of Redux.

getSocketResponseHandlerList -> Return all function that handles the socket response. all functions stored here accepts a JSON parameter { store, response }. NOTE: This is created for specific beheviour.

Decorators:

  1. @reducer - Instead of decorating the class, this is more on registering the class for it to be retrieved using getReducers. Parameter:

  2. name -> name that would be use for the class reducer when passed to createStore.

  3. parentName -> Will be used if the reducer will be combined with multiple reducers. { parentName: combineReducers({ name: ... }) }

  4. @emitAction -> This is a function decorator, this must return a payload {m: string, v: any} that will be passed to emit.

Parameters:

  1. name -> name of the action type. This method will also automatically dispatch a success or fail actions.

If you pass "awesome", then the success will be "awesome_SUCCESS" and the fail will be "awesome_FAIL".

NOTE: It is expected that the project uses Redux along with Redux-Thunk and a extra argument, name emit is passed.

When calling method decorated with this, a dispatch event will be passed using the name parameter as type of the event dispatch. The payload of the data can also be passed to the initial dispatch by passing a second boolean parameter to @emitAction.

##NOTE for @emitAction This is made specifically to a behaviour that is currently used on a project. This might not be usable to others.

Example:

  //'awesome' string will be dispatch as action.
  @emitAction('awesome')
  doSomethingAwesome() {
    return {
      m: '/api',
      v: { name: 'decorator' }
    }
  }