[Bug Report] immediate:false in useRequest doesn't seem to work about alova HOT 7 CLOSED

@proddy I will see it tomorrow. now I have to go to sleep.🥱

from alova.

@proddy Now the bug is fixed. the reason is react strict mode will emit useEffect twice and the second time is going to send a request

from alova.

Hi proddy! thanks for supporting alova.☺️
If it's the same as what you describe, I think it should be a bug. but this case is already passed unit test, see here(second test)
so, you can provide a demo which can reproduce the bug, I will resolve it as soon as possible.

from alova.

Hey, thanks for the quick response. I cooked up a really small sandbox app here . When you run it, and monitor the traffic using the browser dev tools->Network you'll see it'll always make the Request even if the immediate flag is false. Hope it helps!

from alova.

🎉 This issue has been resolved in version 2.5.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from alova.

@proddy Now the bug is fixed. the reason is react strict mode will emit useEffect twice and the second time is going to send a request

Thanks for the quick fix, much appreciated. I was thinking last night too it may be related to the Strict mode so good catch. I'm really loving this library.

from alova.

😁😁😁
Another small secret is that alova's shared request can prevent sending request twice during initialization in react strict mode

from alova.