-
Notifications
You must be signed in to change notification settings - Fork 199
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
Could I turn off the tracking component from a specific library? #114
Comments
Hey! |
@vzaidman Yeah, this my current configuration.
|
I can't think of any better way than something like (i didn't try it):
|
Hey @vzaidman, thank for your suggestion. I've added a condition before set whyDidYouRender to false.
But it still doesn't work. I think it still couldn't turn off warning of the component inside Table component. |
open the arrow from the log, right click the "body" component and see where it comes from. |
@vzaidman |
got to import it and set I will think of a better way meanwhile. |
@vzaidman I don't know why but it still doesn't work although I've imported directly and set https://codesandbox.io/s/turn-off-specific-component-in-whydidyourender-wdm64?file=/wdyr.js |
damn, sadly |
i need to research it a little more. |
Would it be possible to use the exclude option with a RegEx to workaround it in the meantime?
|
Yes it would, but just in case the library exports components with unique enough names. |
Could I turn off the tracking component from a specific library?
After upgrade to Ant Design v4, the Table component's specification has changed as well. So I need to turn
whyDidYouRender
warning off for this component.I know that we could turn off whyDidYouRender by using
whyDidYouRender = false
on a specific component. How could we do the same for a specific component from the library like Ant Design?I don't want to set exclude in the configuration of whyDidYouRender, because of the re-rendered component name is quite common (for instance,
Body
,undefined
)Thank you in advance.
The text was updated successfully, but these errors were encountered: