-
Notifications
You must be signed in to change notification settings - Fork 47.9k
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
Add component stack to the contentEditable warning #8497
Comments
We should add component stack to it, just like other warnings have it. |
@gaearon I'd like to try this one out. I'm a first-time contributor for the React project so some more pointers would be appreciated! |
Here is an example of a warning that includes component stack. Here is how we test such warnings. Here is the contentEditable warning. As you see, it doesn't include the stack. Add it there. Here is the relevant test. Change it to also test the warning message (not just a single word like now) and for the presence of the stack. Hope this helps! |
👍 Thank you! I'll give it a shot later today |
feature
It would help heaps if I would know which component is causing this.
The text was updated successfully, but these errors were encountered: