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

crud-list-reducer

v1.2.1

Published

Managing API conn with list

Downloads

4

Readme

crud-list-reducer

Problems Statement:

  • You want to manage the list of homogenous object structure

  • Each item could be identified by a unique id, or function that return a unique value

  • It acts as single source of truth, but capability to be synchronized with API calls

  • localized states:

{
    localItemDict: {},  // state at local
    syncedItemDict:{},  // state that marked as synchronized
    toBeAddedList:[],   // to be added list, which is still unable to be keyed into dictionary/map
    isLoading: false    // loading flag that changes while calling API
}

Sample

You could do something like this


let userReducerPackage = CrudListReducerGenerator.Reduce({
    prefix: 'user',
    singular: 'User',
    plural: 'Users'
})
.identifiedBy((user) => user.id)
.onPopulatingSyncedItems(async (sex) => {
    if(sex) {
        return await fakeApiServer.getUsersByGender(sex)
    } else {
        return await fakeApiServer.getUsers()
    }
})
.onAddingItem( async (user) => {
    var newId = await fakeApiServer.addUser(user)
    return {
        ...user,
        id:newId
    }
})
.onAddingItems( async (users) => await fakeApiServer.addUsers(users))
.onRemovingItem( async (user) => {
    await fakeApiServer.removeUser(user)
    return user
})
.onRemovingItems( async (users) => {
    await fakeApiServer.removeUsers(users)
    return users
})
.onUpdatingItem( async (user) => {
    await fakeApiServer.updateUser(user)
    return user
})
.onUpdatingItems( async (users) => {
    await fakeApiServer.updateUsers(users)
    return users
})

// yes, custom action. must return key value pair of user
.onExecutingCrudSyncedItems ('markAsDeceased', async (name) => {
    var user = await fakeApiServer.getUserWithName(name)
    user = await fakeApiServer.markUserAsDeceased(user.id)
    return {
        [user.id]: user
    }
})

// return id with value null would imply deletion
.onExecutingCrudSyncedItems ('removeDeceasedUsers', async (name) => {
    var deceasedUsers = await fakeApiServer.removeDeceasedUsers()
    var userDict = {}
    deceasedUsers.forEach((u) => {
        userDict[u.id] = null
    })
    return userDict
})


.generate()

which generate:

  • reducer

  • function to generate actions

    it will generate the following actions:

    • populateUsers

    • addUser

    • addUsers

    • removeUser

    • removeUsers

    • updateUser

    • updateUsers

    • markAsDeceased

    • removeDeceasedUsers

    as well as function that will always be available

    • populateUsersLocally,

    • addUserLocally,

    • addUsersLocally,

    • modifyUserLocally,

    • modifyUsersLocally,

    • removeUserLocally,

    • removeUsersLocally,

    • setUserLocally,

    • setUsersLocally

Internally, every action will call one or more of these reducer actions

  • user.startLoading

  • user.stopLoading

  • user.set

  • user.setSynced

  • user.setSyncedByKeys

  • user.startAdding

  • user.stopAdding

  • user.startRemoving

  • user.stopRemoving

##other static methods:

export {
  CrudListReducerGenerator,
  
  
  /**
   * getInitialStateTemplate(), return:
   * {
   *     localItemDict: {},  // state at local
   *     syncedItemDict:{},  // state that marked as synchronized
   *     toBeAddedList:[],   // to be added list, which is still unable to be keyed into dictionary/map
   *     isLoading: false    // loading flag that changes while calling API
   * }
   */
  getInitialStateTemplate,

  /**
   * getLocalList(store.dispatch), return:
   * localItemDict, which is flattened into list and concatenated with toBeAddedList
   */
  getLocalList,

  /**
   * getSyncedList(store.dispatch), return:
   * syncedItemDict, which is flattened into list
   */
  getSyncedList,

  /**
   * isLoading(store.dispatch), return:
   * return isLoading flag
   */  
  isLoading,

  /**
   * getComputedValues(store.dispatch), return:
   * return {
   *    syncedList,
   *    localList,
   *    isLoading
   * }
   */  
  getComputedValues
}

##FOR DETAIL IMPLEMENTATION, check /sample