Version: 6.12.2

Themes

A theme is a type of style which is applied to the entire app. It allows you to declare a consistent style to all Navigation components such as the TopBar and BottomTabs and also to system elements like the StatusBar and NavigationBar.

Applying a theme#

Themes are applied using Navigation.setDefaultOptions() which must be called before Navigation.setRoot() is called.

// Set the default topBar background color to red
Navigation.setDefaultOptions({
  topBar: {
    background: {
      color: 'red'
    }
  }
});

// That stack's topBar background color will be red, as is set in default options
Navigation.setRoot({
  root: {
    stack: {
      children: [
        ...
      ]
    }
  }
});

Conditional themes with Options Processor#

Some style requirements can't be facilitated with the defaultOptions api. For example, an app may have a unique theme for screens displayed in a modal or require that modals have a default dismiss button in the TopBar. An Options Processor allow us to mutate the options object of each screen and layout right before they are displayed.

Lets see how we can leverage this API to add a dismiss button to the TopBar when showing a modal.

import {
  CommandName,
  Navigation,
  NavigationButtonPressedEvent,
  OptionsTopBar,
} from 'react-native-navigation';

Navigation.addOptionProcessor<OptionsTopBar>(
  'topBar',
  (topBar: OptionsTopBar, commandName: CommandName): OptionsTopBar => {
    if (commandName === CommandName.ShowModal) {
      if (!topBar.leftButtons) {
        topBar.leftButtons = [
          {
            id: 'dismissModalButton',
            icon: require('dismissIcon.png'),
            color: 'black',
          },
        ];
      }
    }
    return topBar;
  }
);

// Now that each modal has a dismiss button, let's handle the button press event and dismiss the modal when needed.
Navigation.events().registerNavigationButtonPressedListener(
  (event: NavigationButtonPressedEvent) => {
    if (event.buttonId === 'dismissModalButton') {
      Navigation.dismissModal(event.componentId);
    }
  }
);

The Options Processors can also be used to set default options for buttons, here's how:

import { CommandName, Navigation, OptionsTopBarButton } from 'react-native-navigation';

Navigation.addOptionProcessor<OptionsTopBarButton>(
  'topBar.rightButtons',
  (rightButtons: OptionsTopBarButton[], commandName: CommandName): OptionsTopBarButton => {
    return rightButtons.map((button) => ({
      ...button,
      fontFamily: 'helvetica',
      fontSize: 16,
      color: 'red'
  }));
);

Conditional themes with Layout Processor#

Layout Processor is similar in concept to the Options Processor discussed above. While Options Processor is invoked for each options object, Layout Processor is invoked once on the entire (layout)['../api/layout-layout/'] tree passed to the Navigation command.

Through the Layout Processor we can access the layout and it's children, and mutate both options and passProps before the layout is displayed. In this example we iterate on the stack's children and set a dark TopBar color according to a theme property in the child's props.

import { Layout, Navigation } from 'react-native-navigation';

interface ScreenProps {
  theme: 'light' | 'dark';
}

function isScreenProps(obj: unknown): obj is ScreenProps {
  return typeof obj === 'object' && obj !== null && typeof (obj as ScreenProps).theme === 'string';
}

Navigation.addLayoutProcessor((layout: Layout, commandName: string) => {
  layout.stack?.children?.forEach((child) => {
    if (!child.component) {
      return;
    }
    const props = child.component.passProps;
    if (isScreenProps(props) && props.theme === 'dark') {
      child.component.options = {
        topBar: {
          background: {
            color: 'black',
          },
        },
      };
    }
  });
  return layout;
});

Changing theme dynamically#

Apps can have multiple themes and sometimes you might need to change theme dynamically. To change current theme, simply call Navigation.setDefaultOptions() with updated theme options, following that with a call to Navigation.setRoot(). The reason we need to setRoot once more is because Navigation.setDefaultOptions() does not apply options to screens which had already been created.