-
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
Code snippet in docs unexpectedly throws #173
Comments
@shawninder are you planning on submitting a PR for this? |
I don't think this is actually a problem, is it? The code in Null checks before accessing refs are a good idea if the code in question might execute before a mount or after an unmount (eg as the result of a timer, promise, or network request) but I don't think it's actually a problem in this case. Maybe I'm misunderstanding this? 😄 |
Hmm I guess you are right @bvaughn, the problem I mention would only occur if you place the two inputs in different components, allowing the button to be mounted while the other input is not. So no, @Ethan-Arrowood, I will not submit a PR for this. |
No worries at all. I appreciate you bringing this to our attention, just in case. 👍 |
Co-Authored-By: CaiqueMOliveira <caique.m.oliveira.br@gmail.com> * add missing single quotation on the end of the test description
Bug Report
The docs present an example code snippet which crashes the js process. See https://reactjs.org/docs/refs-and-the-dom.html#adding-a-ref-to-a-dom-element
In particular, notice the highlighted parts of the code snippet and the first sentence under the snipppet, which reads "React will call the ref callback with the DOM element when the component mounts, and call it with null when it unmounts.".
this.textInput = null;
.focusTextInput
method will dothis.textInput.focus();
.this.textInput
is null, it's really doingthis.null.focus();
.focus
is not a method ofnull
, so this will throwI would suggest adding a little guard for this in the code snippet so that people can copy-paste without worry, replacing this:
with this:
or something like this.
This was found in the docs for React v16.0.0
The text was updated successfully, but these errors were encountered: