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

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

На главную

❌ Avoid using objects as dependencies in React.useEffect() ✅ Instead use the primitive keys

43,042 просмотров • 1 год назад •via X (Twitter)

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

Фото профиля George Moller
George Moller1 год назад

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

Фото профиля SecurityPal
SecurityPal1 год назад

“When something breaks, be transparent, own it, fix it. And it's really about how you respond to it.” @WilHarm3 (@craft_ventures) emphasizes the importance of transparency and responsiveness when things go wrong. Watch the episode here:

Фото профиля skylerdj👻
skylerdj👻1 год назад

or be toxic and wrap the object with `JSON.stringify()`

Фото профиля Gustavo AL.
Gustavo AL.1 год назад

Good advice, but in this case you might not need an useEffect. Like this article of official documentation said, a useEffect is to synchronize external state (API, storage, DOM) with internal state of React.

Фото профиля Mohammad, the Dev one.
Mohammad, the Dev one.1 год назад

Here,understanding the concept of passed by value and passed by reference shines. When we put an passed by reference item into the dependency array, it makes the useEffect to re-run on reach re-render. Good point 👍

Фото профиля Alejandro
Alejandro1 год назад

if you use const {userId} = params everything should be the same no?

Фото профиля Ethan_AI Marketer for 𝕏
Ethan_AI Marketer for 𝕏1 год назад

Have you tried using primitive keys in your useEffect dependencies? It can really help avoid unnecessary re-renders. I’ve seen it make a big difference in performance.

Фото профиля nome
nome1 год назад

i want a react job i am working in react since 2 years i have strong grip on react ,redux , tailwindcss,material ui ,ajax ,axios ,jsx , props , hooks ,state management , ui responsive design

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