GithubHelp home page GithubHelp logo

Comments (4)

rickhanlonii avatar rickhanlonii commented on April 27, 2024 1

@Janelaxagh please don't reply with chatgpt or whatever answers, I've seen this on a few issues and it's often wrong. I've hidden your comment, because it's very wrong this time.

from react.

pgsandstrom avatar pgsandstrom commented on April 27, 2024 1

Sorry about the silly mistake. The bug is still present even with a fixed dependency array. I opened a new issue with a codesandbox example to make it clearer: #28304

from react.

Janelaxagh avatar Janelaxagh commented on April 27, 2024

This seems like an issue related to the timing of when the useEffect hook captures the variables (a and b) and when it executes. React doesn't guarantee the exact order in which effects are executed, especially in scenarios like yours where quick updates or multiple changes are occurring.

The behavior you're experiencing might occur due to the asynchronous nature of how React batches updates and executes effects. The effect captures the values at the time it's created, but by the time it runs, those values might have changed, especially if changes are happening rapidly.

One potential way to address this is to use a ref to hold the variables, capturing their current values at the time the effect runs. This way, you can ensure the effect uses the most recent values.

Here's an example:

import { useEffect, useRef } from 'react';

function useWtf(a?: string, b?: string) {
  const aRef = useRef(a);
  const bRef = useRef(b);

  useEffect(() => {
    aRef.current = a;
    bRef.current = b;

    console.log("inside effect", aRef.current, bRef.current);
  }, [a, b]);
  
  console.log("outside effect", a, b);
}

By using useRef, you maintain a reference to the latest values of a and b. This doesn't change the asynchronous nature of React, but it ensures that when the effect runs, it uses the most recent values captured in the ref objects.

from react.

rickhanlonii avatar rickhanlonii commented on April 27, 2024

@pgsandstrom the scope is stale because your effect uses a variable b but doesn't include in the the dependencies. If you enable the react-hooks/exhaustive-deps lint rule, you'll see the error that catches this (sandbox):

React Hook useEffect has a missing dependency: 'b'. Either include it or remove the dependency array.
(react-hooks/exhaustive-deps)

from react.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.