Загрузка видео...

Не удалось загрузить видео

На главную

❌ Avoid deriving state in useEffect in React, this can create multiple unnecessary render phases. ✅ Instead derive the state directly in the event handler, this way you'll have one single render phase. ↓

39,326 просмотров • 2 лет назад •via X (Twitter)

Комментарии: 9

Фото профиля George Moller
George Moller2 лет назад

I've been working professionally with React for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video animations just like this one. Check them out ↓

Фото профиля Web-Dev-Codi
Web-Dev-Codi2 лет назад

Informative as always. Thank you

Фото профиля George Moller
George Moller2 лет назад

Glad you found it informative!

Фото профиля NidhiSharma | React Dev
NidhiSharma | React Dev2 лет назад

Sometime overuse of useEffect cause extra re-render we should avoid useEffect where ever possible. Nice sharing.

Фото профиля joey finkel
joey finkel2 лет назад

But this would only work if the state that’s being updating is supposed to be updated by an event handler. For example, a piece of state you want updated on first render would still have to be the effect, right?

Фото профиля George Moller
George Moller2 лет назад

Do you have an example I can take a look? Unless you are fetching data or connecting to an external system first why would you need to update a state variable in first render?

Фото профиля Bee Network - Vietnam 🇻🇳
Bee Network - Vietnam 🇻🇳2 лет назад

great

Фото профиля George Moller
George Moller2 лет назад

Hey do you have an email or contact where I can send you the PP discount?

Фото профиля George Moller
George Moller2 лет назад

@Setback_King 😊

Похожие видео