How does setting and merging of options actually works?

📚 Documentation

Currently, we can set component options by multiple ways:

1. Navigation.setDefaultOptions
2. Navigation.mergeOptions
3. Layout definition (via Navigation.push, Navigation.setRoot...)
4. Static options on component

My questions are:

1. When options are set to the component for the first time?
   - It is in time of component registering (Navigation.setDefaultOptions),
   - or before mounting when no animation happened yet (Navigation.setRoot...),
   - or at any time (Navigation.mergeOptions)?
2. How does the merging process works? What takes the precedence? What is the order?
3. Does merging algorithm handles every property anywhere deep in the layout, or does it only replaces whole sections (like BottomTabsOptions, TopBarOptions etc.)?
4. Can Navigation.setDefaultOptions be called multiple times?
5. Does calling Navigation.setDefaultOptions update already mounted and appeared component? And does it trigger the whole merging process as defined in question no. 2?
6. Does calling Navigation.mergeOptions trigger the whole merging process as defined in question no. 2? That means that it for examples merges with default options - if defined.

It would be great to have some diagram demonstrating the whole flow.

Thanks for reply.

Have you read the Contributing Guidelines on issues?

Partially

[aliraza-noon]

merging of options is tricky business, we were initially using react-navigation we switched to RNN for performance reasons after months of development to find out there are lot corner cases that are not handled options being one of them.

1. changing the topbar icon colors with merge options does not work (android)
2. we can't change icon images (android)
3. spacing is messed up on both (ios, android)
   ... list goes on

eventually we switched back to react-navigation, we would like to switch to RNN we have branch we are maintaining hoping these issues will be resolved someday. its complete mess right now