Ok, i\'ll try and make this quick because it SHOULD be an easy fix...
I\'ve read a bunch of similar questions, and the answer seems to be quite obvious. Nothing I wo
Reason is setState is asynchronous, you can't expect the updated state
value just after the setState
, if you want to check the value use a callback
method. Pass a method as callback that will be get executed after the setState
complete its task.
Why setState is asynchronous ?
This is because setState
alters the state
and causes re rendering. This can be an expensive operation and making it synchronous
might leave the browser unresponsive.
Thus the setState
calls are asynchronous
as well as batched for better UI experience and performance.
From Doc:
setState() does not immediately mutate this.state but creates a pending state transition. Accessing this.state after calling this method can potentially return the existing value. There is no guarantee of synchronous operation of calls to setState and calls may be batched for performance gains.
Using callback method with setState:
To check the updated state
value just after the setState
, use a callback method like this:
setState({ key: value }, () => {
console.log('updated state value', this.state.key)
})
Check this:
class NightlifeTypes extends React.Component {
constructor(props) {
super(props);
this.state = {
barClubLounge: false,
seeTheTown: true,
eventsEntertainment: true,
familyFriendlyOnly: false
}
}
handleOnChange = (event) => { // Arrow function binds `this`
let value = event.target.checked;
if(event.target.className == "barClubLounge") {
this.setState({ barClubLounge: value}, () => { //here
console.log(value);
console.log(this.state.barClubLounge);
//both will print same value
});
}
}
render() {
return (
)
}
}
ReactDOM.render( , document.getElementById('app'))