¿De verdad necesitas useEffect para eso? #reactjs #reactnative #nextjs

In this ReactJS video, I'll discuss several cases where you don't need to use the `useEffect` hook to implement a feature. 👨🏼‍💻 Support me on Patreon:   / latteandcode   💛 The folks at Garaje de Ideas sponsor Latte and Code and are looking for talent: http://bit.ly/garaje-tech-talento ☕️ Buy me a coffee: https://www.buymeacoffee.com/latteand... 🔗 https://react.dev/learn/you-might-not... This video is inspired by the React documentation article "You Might Not Need an Effect," which covers various situations where using the `useEffect` hook isn't necessary. [00:00] Introduction [01:21] The key property [06:21] How to avoid unnecessary renders with useEffect and fetch [09:56] What happens if we invoke setState in the component body In this React video, we'll see how we can use the "key" property of components to reset the state instead of using the useEffect hook. This will allow us to avoid unnecessary renders and improve our application's performance. We'll also learn how to avoid unnecessary renders when consuming an API using fetch and useEffect, preventing renders that don't provide any information to the user. And finally, we'll see that, contrary to popular belief, there's no problem invoking setState in the component body to update the state. However, we'll have to be careful not to create an infinite loop. 💛 I hope you enjoy it!