Screens under FluidNavigator don't respect navigationOptions hence i can't customise header?

[zloz]

Header couldn't be customise under FluidNavigator as it doesn't respects navigationOptions, can't find any relevant example also.

navigationOptions:({navigation,screenProps}) =>{ return{ headerStyle:StackNavigationHeader.headerStyle({navigation}), headerLeft:StackNavigationHeader.headerLeftDrawer({navigation,screenProps}), headerRight:StackNavigationHeader.courseHeaderRight({navigation,screenProps}), headerTitle:StackNavigationHeader.headerTitle({navigation}) } },

[chrfalch]

Hi @zloz: FluidNavigator does not have a header as stated in the documentation, so this won't work. Wrap it in a parent StackNavigator to customize the header.

[zloz]

but that would restrict me to have same header(even if customised under stacknavigator) in all the screens under fluid navigator , i want to have a different header for screens under fluid navigator

[chrfalch]

Yes, but due to The complexities involved with headers this is unfortunately not feasible - you could bind the parent header to make it more dynamic. FluidNavigator is unfortunately not a stack navigator with header - it is a navigator for transitions that happens to use a stack router underneath.

…

20. jun. 2018 kl. 16:21 skrev binaryInspirations ***@***.***>: but that would restrict me to have same header(even if customised under stacknavigator) in all the screens under fluid navigator , i want to have a different header for screens under fluid navigator — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.

[muhaimincs]

I have applied it just like your suggestion. But I'm having flickering issue when hide the header on second screen.

static navigationOptions = ({navigation}) => {
    const {state: {index = 0} = {}} = navigation;
    if (index > 0) return {header: null};
    return {
      title: 'UMRAHTI',
    };
  };