-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Bugs and issues umbrella #84
Comments
Ooh, I'll grab the issue "Mark mockComponent as legacy and unnecessary" assuming it's to change this section: https://reactjs.org/docs/test-utils.html#mockcomponent |
Okay it's yours |
Made a PR for " |
@bvaughn the last two issues had been solved, maybe someone forgot to tick them off at facebook/react#8035 . |
Yup! You're right! String refs are mentioned here and it looks like all of the forms examples show controlled components now. Thanks for pointing this out! Description has been updated. |
I added an issue about the docs in the wrong place so it was closed. Hopefully this is the right place: facebook/react#11221 |
Hey @shawninder 😄 This is the right repo. However, would you be willing to file your bug report as a new issue in this project? (Seems like this umbrella has outlived its usefulness.) |
cc: @cezaraugusto vou aprovar essa PR. Uma vez que, ela é extremamente pequena e não há mudanças a serem feitas.
We just completely rewrote docs in facebook/react/issues/7864.
They're bound to cause some issues, have some mistakes, etc.
Let's keep this issue as an umbrella for all problems we're discovering after the initial rollout.
Claimable
In-progress
mockComponent
as legacy and unnecessary (react/issues/2499#issuecomment-94044857)shallowCompare
on Addons page should recommendPureComponent
insteadIf you'd like to claim any of the above items, leave a comment and we'll update this issue!
Migrated from facebook/react/issues/8035
The text was updated successfully, but these errors were encountered: