Skip to content

Conversation

@guyca
Copy link
Collaborator

@guyca guyca commented Oct 23, 2019

Until now, mergeOptions would merge with parent controller only if mergeOptions was called with
a componentId. This commit fixes the issue and makes options merge correctly even when called with a layoutId.

guyca added 2 commits October 23, 2019 16:47
Until now, mergeOptions would merge with parent controller only if mergeOptions was called with
a componentId. This commit fixes the issue and makes options merge correctly even when called with a layoutId.
@guyca guyca merged commit 0dd3315 into master Oct 24, 2019
@guyca guyca deleted the mergeOptionsOnParentControllers branch October 24, 2019 05:58
guyca added a commit that referenced this pull request Oct 31, 2019
Until now, mergeOptions would merge with parent controller only if mergeOptions was called with
a componentId. This commit fixes the issue and makes options merge correctly even when called with a layoutId.

# Conflicts:
#	lib/android/app/src/main/java/com/reactnativenavigation/viewcontrollers/ChildController.java
#	lib/android/app/src/main/java/com/reactnativenavigation/viewcontrollers/ComponentViewController.java
#	lib/android/app/src/test/java/com/reactnativenavigation/mocks/SimpleViewController.java
#	playground/android/build.gradle
guyca added a commit that referenced this pull request Oct 31, 2019
vshkl pushed a commit to vshkl/react-native-navigation that referenced this pull request Feb 5, 2020
Until now, mergeOptions would merge with parent controller only if mergeOptions was called with
a componentId. This commit fixes the issue and makes options merge correctly even when called with a layoutId.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants