-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
[Bugfix] Within NavigatorIOS, navigator.replace doesn't update the navigation bar. #3516
[Bugfix] Within NavigatorIOS, navigator.replace doesn't update the navigation bar. #3516
Conversation
rocman
commented
Oct 19, 2015
- let the RCTNavItem refer to the NavigationBar and the NavigtaionItem, so that it can forward the modifications to them. And such, to fix the bug that props.navigator.replace does not update the NavigationBar.
- Provide a update method to modify the current route
…vigation bar. 1. let the RCTNavItem refers to the NavigationBar and the NavigtaionItem, so that it can forward the modifications to them. And such, to fix the bug that props.navigator.replace does not update the NavigationBar. 2. Provide a update method to modify the current route
When there is no component or passProps on the route, skip updating the component. So as to allow modifying the navigation bar without rerendering the component. And so to make it possible to set up the navigation bar according to the state in the component render, which is important.
By analyzing the blame information on this pull request, we identified @ide, @nicklockwood and @mrspeaker to be potential reviewers. |
@rocman updated the pull request. |
@rocman updated the pull request. |
@rocman updated the pull request. |
Somebody? |
@@ -13,6 +13,9 @@ | |||
|
|||
@interface RCTNavItem : UIView | |||
|
|||
@property (nonatomic, assign) UINavigationBar *navigationBar; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are pointers, they should be strong or possibly weak, but definitely not assign.
following @nicklockwood’s suggestions, i’ve adjusted the property declarations for navigationBar and navigationItem, and simplified the logics that adjust the the buttons.
@rocman updated the pull request. |
@rocman updated the pull request. |
@rocman updated the pull request. |
@rocman updated the pull request. |
@rocman updated the pull request. |
@rocman updated the pull request. |
I don't understand why the checks failed... |
will version 0.14.0 will fix this ? |
I'm suffering from the failure of ci build checks and don't know how to fix it. So the pull request is still uncommitted. |
@rocman updated the pull request. |