Stop Using `useEffect` for Data Fetching—Please, I Beg You
You're staring at your screen, debugging why your dashboard keeps showing yesterday's data even after you've changed the filter. Your useEffect dependency array looks like a crime scene. You've got three useState hooks just to manage loading, error, and data.
- ▪You're staring at your screen, debugging why your dashboard keeps showing yesterday's data even after you've changed the filter.
- ▪Your useEffect dependency array looks like a crime scene.
- ▪You've got three useState hooks just to manage loading, error, and data.
DEV.to (Top) files mainly under programming. We currently carry 4,900 of its stories.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 491136) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Oge Obubu Posted on Jul 26 Stop Using `useEffect` for Data Fetching—Please, I Beg You #webdev #programming #productivity #javascript The Scene It's 2 AM. You're staring at your screen, debugging why your dashboard keeps showing yesterday's data even after you've changed the filter. Your useEffect dependency array looks like a crime scene. You've got three useState hooks just to manage loading, error, and data.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
