MaxInterview - usestate giving previously update data

showing results for - "usestate giving previously update data"

25 Feb 2017

1While React's setState is asynchronous (both classes and hooks), and it's 
2tempting to use that fact to explain the observed behavior, it is not the
3reason why it happens.
4
5TLDR: The reason is a closure scope around an immutable const value.
6
7Solutions:
8read the value in render function (not inside nested functions):
9
10useEffect(() => { setMovies(result) }, [])
11console.log(movies);
12
13add the variable into dependencies (and use the react-hooks/exhaustive-deps eslint rule):
14
15useEffect(() => { setMovies(result) }, [])
16useEffect(() => { console.log(movies) }, [movies])
17
18use a mutable reference (when the above is not possible):
19
20const moviesRef = useRef(initialValue)
21useEffect(() => {
22    moviesRef.current = result
23	console.log(moviesRef.current)
24}, [])

similar questions

update state in usestate hook componentdidupdate in hooks update object in react hooks get option value in react by usestate setstate not updating state immediately react update state hook with previous value force update react hooks update usestate using function onpress not working with usestate react native updating one state of an object of states react usestate replace componentwillmount with hooks useeffect not working array changes component did update hooks usestate access previous state react hooks update parent state from child react usestate functional update set state giving previously update data javascript react usestate update object

queries leading to this page

usestate giving previously update data usestate giving previously update data