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

combine-section-selectors

v1.0.0

Published

Combine selectors from state to one set of selectors. Useful with redux and combineReducer or combine-section-reducer

Downloads

4

Readme

combine-section-selectors

Combines selectors into one object with proper path handling.

API

Every selector should have get prefix in name! E.g. getMyValue.

Also names of all selectors should be uniq.

default export:

(modules: {[string]: {[string]: Function}}) =>
    ({[string]: Function})

Name of module should be exact same as key on where state is stored. So if you have state.users.userId, you should combine selectors for users on "users" key:

const fromState = combineSelectors({
    users: {
        getUser: (users, userId) => users[userId],
    },
});
fromState.getUser({users: {myId: {}}}, `myId`)

Selector implementation gets substate as first argument, and rest args just compied.

Selector from combine gets entire state as first argument, and any rest args.

Also selector implementation gets entire state as last argument. It's same as in combine-section-reducer module.

Example

reducer for counter

const counter = (state = 0, action) => {
    switch (action.type) {
        case `ADD`:
            return state + action.payload;
        default:
            return state;
    }
}
export default counter;

selectors for counter

export const getCount = (state, minusCount) => state - minusCount;

combine

import {combineReducers} from 'redux';
import combineSelectors from 'combine-section-selectors';
import counter from './counter';
import * as fromCounter from './counter.selectors';

const reducer = combineReducers({
    counter,
});

const fromState = combineSelectors({
    counter: fromCounter,
});

const store = createStore(reducer);
store.dispatch({type: `ADD`, payload: 5});
fromState.getCount(store.getState(), 3); // returns 2 (5 in state minus 3 from argument)

Motivation and alternatives

Without such module you should always set path to entity in selector:

const getUser = (state, userId) => state.data.users.entities[userId];

which is awkward, because it makes this selector depending on where substate is connected to entire state.

Or even worse, pass path to substate on every usage of selector:

fromState.getUser(state.data.users, userId);