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

@dynamic-selectors/core

v1.2.1

Published

Dynamic selector functions

Downloads

26

Readme

@dynamic-selectors/core

Selectors with parameters and dynamic dependencies.

See Selector Comparison for a walkthrough.

npm version build status test coverage dependencies status gzip size

Dynamic selectors can access state dynamically and call each other like plain functions, even conditionally or within loops, without needing to register dependencies up-front. Like Reselect and Re-reselect, selectors are only re-run when necessary.

This may be used with a state library like Redux, or on its own as a general memoization util.

For more information or related packages, see the Dynamic Selectors workspace.

Example

import { createDynamicSelector } from '@dynamic-selectors/core';

Dynamic selectors can access state via a deep-get helper:

const getBooksForAuthor = createDynamicSelector((getState) => {
  const books = getState('books');
  const authorFilter = getState('authorFilter');

  return books.filter((book) => book.author === authorFilter);
});

Selectors can call other selectors inline -- even in loops:

const getBookInfo = createDynamicSelector((getState, bookId) => {
  const rawBookData = getState(`bookInfo[${bookId}]`);
  return new Book(rawBookData);
});

const getBooksForAuthor = createDynamicSelector((getState, authorId) => {
  const bookIds = getState(['booksByAuthor', authorId]);
  return bookIds.map((bookId) => getBookInfo(bookId));
});

getBooksForAuthor(authorId) is cached, and will only rerun when its dependencies change: state.booksByAuthor[authorId] or one of the getBookInfo(bookId) calls it made. The return value is cached per authorId.

getBookInfo(bookId) is cached similarly, and will only rerun when state.bookInfo[bookId] changes. The same cache is used if you call getBookInfo(state, bookId) directly.

Features

Comparison between Reselect and Dyanamic Selectors

API

Your selector function receives two arguments: getState and params (optional). Any additional arguments provided when calling the selector will be passed through as well, although they don't do anything.

  • getState<T>(path: string | Array<string>, defaultValue?: T) lets you access any path in state. It works like lodash's get.
  • params (optional) can be anything you want, but it's best as either a single primitive value or a flat object containing a few values -- similar to route params.

The selector's results will be cached using params. See Selector Options to customize the cache key generation.

Calling a dynamic selector

To call a selector, pass it your state and params (optional).

When calling one selector from within another, pass params only.

const getRawList = createDynamicSelector((getState, { listId }) => {
  return getState(`lists.${listId}`);
});

const getSortedList = createDynamicSelector((getState, { listId, sortField }) => {
  // `state` is automatically pased through when one selector calls another
  const rawList = getRawList({ listId });
  if (rawList && sortField) {
    return sortBy(rawList, sortField);
  }
  return rawList;
});

getSortedList(state, { listId: 123, sortField: 'title' });

Typings

In Typescript, the return type of the selector -- as well as any typings for its params or additional arguments -- will be inferred from the type of the function passed into it.

const selector1 = createDynamicSelector(() => 3);
const value1 = selector1(); // type: number

const selector2 = createDynamicSelector(() => 'Hello');
const value2 = selector2(); // type: string

const selector3 = createDynamicSelector(
  (getState, userId: number): UserModel => getState(['users', userId]),
);
const value3 = selector2(state, 123); // type: UserModel
const value4 = selector2(state, true); // error

Inside a selector, getState can be assigned a specific return type. (Default: unknown)

createDynamicSelector((getState) => {
  const value1 = getState<number>('path.to.number'); // type: number
  const value2 = getState<boolean>('path.to.boolean', false); // type: boolean
  const value3 = getState<string>('path.to.string', false); // error: defaultValue doesn't match string
});

Additional selector properties

These are attached to the selector function returned by createDynamicSelector.

selector.getCachedResult()

If there's a usable cached value for the current state and params, it will be returned. Returns undefined otherwise.

Call this just like the selector itself (i.e., (state, params) from outside, (params) from inside a selector).

selector.hasCachedResult()

Returns a boolean to indicate whether or not there's a usable value in cache for the current state and params.

Call this just like the selector itself (i.e., (state, params) from outside, (params) from inside a selector).

selector.resetCache()

Re-initializes the cache of previous results.

selector.getDebugInfo() (development only)

Returns an object with statistics about the selector's activity (runs, cache-checks, results, etc.)

selector.isDynamicSelector (always true)

The canonical way to detect that a function is a dynamic selector.

Selector Options

When creating a selector, you can pass a second argument with options to customize its behavior.

const mySelectorFn = createSelectorFn(fn, options);

compareResult (function(oldValue, newValue): boolean, default: shallowEqual)

After a selector runs, compares its previous cached value to the newly-returned value. Return true to discard the new value and reuse the previous value instead. This is useful for selectors that return arrays or other objects which may be new instances but do not actually contain new values.

createResultCache (function(): DynamicSelectorResultCache, default: plain object)

Used to customize the cache where results are stored. The cache must implement get(cacheKey: string) and set(cacheKey: string, value: any). To limit the cache size or cache time using Limited-Cache you would customize this like:

createDynamicSelector(fn, {
  createResultCache: () => LimitedCache({ maxCacheSize: 100, maxCacheTime: 60 * 1000 }),
});

debug (boolean | string, default: false, development only)

Verbose output: logs all selector activity to the console (runs, cache-checks, results, etc).

displayName (string, default: displayName of your function)

Sets the displayName of the returned selector function, and includes it in verbose debug output (if enabled.)

getKeyForParams (function(params): string, default: JSON.stringify)

Generates a string cache key that represents the params. To get constant hashes even when object properties are in a different order from one call to the next, you would customize this like:

Example using node-object-hash:

var hashSortCoerce = hasher({ sort: true, coerce: true });
createDynamicSelector(fn, {
  getKeyForParams: (params) => JSON.stringify(hashSortCoerce(params)),
});

Example using object-hash:

createDynamicSelector(fn, {
  getKeyForParams: hash,
});

onError (function(error, selectorArgs, selectorFn): any, default: null)

Called if the selector function throws an exception. This may recover from the exception -- and supply a new return value for the selector -- by returning any non-undefined value.

If onError is not set, or if it does not return a value when it runs, then the error will be re-thrown.

State Options

In addition to the per-selector options above, you can set state-level options which control the selectors' interactions with state and with other selectors.

This gives you a new selector-creating function: use that instead of the default createDynamicSelector.

This becomes a "zero dependencies" library if you override the default options to not use shallowEqual and lodash's get.

const mySelectorFactory = dynamicSelectorForState(stateOptions);
const mySelectorFn = mySelectorFactory(fn, options);

Each distinct stateOptions should represent a separate store or type of state. You may mix-and-match selectors for different stateOptions, but this may not work as expected: please contact me if you're doing that because I'd love to know more about your specific use case.

compareState (function(oldState, newState): boolean, default: ===)

Compares the current state to the state a selector last ran for. Return true to indicate that state is unchanged. A selector that's called with the same state and params will always use its cache.

get (function(state, pathString, defaultValue?): T, default: _.get)

Accessor to retrieve a value from the state. The path will always be a string. To completely avoid lodash, you can customize this to use something like object-path or tiny-get instead.

defaultSelectorOptions (selector options, default: options)

The default, base options that will be used for each selector (unless overridden when creating the selector.)