You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, this causes a rerender and also resets my refs.
<SearchDropdown ref={this.searchDropdown} />
This ref exists on the first render but is set to null on the second render (caused by Actions.refresh). Is there a better way to set up the navbar before the component is rendered?
The text was updated successfully, but these errors were encountered:
It is wrong approach - declare rightTitle and onRight as static function for your component. You could access to your component ref via Actions.refs.SCENE_NAME#2195
16 авг. 2017 г., в 21:14, Daniel van der Merwe ***@***.***> написал(а):
Ok, it would be useful if you also mentioned that this was a mistake in the example, not my mistake.
e8c5a42#diff-32afed19f718c82f2588a4adaa45100e
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
I'm currently following the example in
Login.js
and doing the following:However, this causes a rerender and also resets my refs.
<SearchDropdown ref={this.searchDropdown} />
This ref exists on the first render but is set to null on the second render (caused by Actions.refresh). Is there a better way to set up the navbar before the component is rendered?
The text was updated successfully, but these errors were encountered: