-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get it work on Expo #58
Comments
BTW, any advice will be welcome ✌️ |
so the library only catches re-renders that "can be prevented" like the one I planted here: how do you do this in this case? you move the array to the top and make the component pure: but the best advice is just to build apps and never prematurely optimize. only use whyDidYouRender for HUGE components like lists and graphics which you want to make sure are not re-rendered too many times :) |
Awesome @vzaidman, |
@vzaidman I'm trying to use this in a component that re-renders 15x when it opens to investigate. I don't see a way to debug it with Expo – should re-render explanations be in the console.logs? It works fine when I do it with Next.js. |
I don't see the logs in expo snack. Is it expected ? |
I don't know what "expo" is and couldn't be able to check it out in the upcoming time as i'm in the process of moving to a new country... |
Hi,
today im trying to work in expo and unable to get it work, something missing?
here the code:
and here the link to snack:
https://snack.expo.io/@outatime/why-did-you-render
Thanks !!!
The text was updated successfully, but these errors were encountered: