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

react-extended-component

v1.1.0

Published

Updating the state of a complex component, without using Redux or Flux in React is very complex process. If you want to update a key in the state object, usually you do it like this

Downloads

8

Readme

react-extended-component

Updating the state of a complex component, without using Redux or Flux in React is very complex process. If you want to update a key in the state object, usually you do it like this

this.setState({
    fname: "Shridhar",
    lname: "Kaushik",
    emails: [
        "[email protected]",
        "[email protected]"
    ]
})

//or for more complex operations like pushing in array or concatenation of other state values, you do it like this

this.setState(prevState=>{
    var prevEmails = prevState.emails
    return {
        name: prevState.fname+" "+prevState.lname,
        emails: prevEmails.concat(["[email protected]"])
    }
})


//to get the values from state
this.state.emails[0]

//Above will throw an error if emails key does not exist on state

But using react extended-component this is a very hassle free process, like below:

//Importing methods
import {updateState, getState} from "react-extended-component"


//For single key simple updation
updateState(this, 'fname', 'Shridhar')

//For multiple key simple updation
updateState(this, {
    fname: "Shridhar",
    lname: "Kaushik"
})

//For single nested keys updation
updateState(this, "user.fname", "Shridhar")

/*
After updation state will be
{
	"user": {
		"fname": "Shridhar
	}
}
*/


//For multiple key simple updation
updateState(this, {
    "user.fname": "Shridhar",
    "user.lname": "Kaushik"
})

/*
After updation state will be
{
	"user": {
		"fname": "Shridhar,
		"lname": "Kaushik"
	}
}
*/


//For custom operation on state object
updateState(this, state=>{
    // Assuming user.emails is an array on the original state object
    state.user.emails.push("[email protected]")
    // Removing value from array using pull from lodash
    _.pull(state.user.emails, "[email protected]")
})

/*
As you can see above, instead of creating a new object to merge with prevState, we're modifying the state object passed into the first parameter, which is a clone of the original state object, thus, it is safe to modify the original variable
*/


//To get a key from state
getState(this, "user.emails[0]")
//Above will return null if any of the parent key is not found and wwill not throw an error


//To get a default value if provided key does not exist on the state
getState(this, "user.emails[0]", '[email protected]')