In < 2.0, I was using Navigation.registerScreen be

I agree <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-

v2.0 Navigation.registerScreen about react-native-navigation HOT 4 CLOSED

wix commented on May 14, 2024

v2.0 Navigation.registerScreen

from react-native-navigation.

Comments (4)

explorigin commented on May 14, 2024 3

Got it sorted. If you want this to be part of the final API, I did it like this: v2.0...twistle:v2.0

My register wrapper function ends up looking like:

function registerWrappedComponent(screenID, generator) {
    const generatorWrapper = () => {
        const InternalComponent = generator();
        return class extends Screen {
            static navigatorStyle = InternalComponent.navigatorStyle || {};
            static navigatorButtons = InternalComponent.navigatorButtons || {};
            constructor(props) {
                super(props);

                this.allProps = {
                    ...props,
                    ...PropRegistry.load(props.screenInstanceID),
                };
            }

            render() {
                return (
                    <SuperProvider store={store} i18n={i18n}>
                        <InternalComponent navigator={this.navigator} {...this.allProps} />
                    </SuperProvider>
                );
            }
        };
    };
    Navigation.registerScreen(screenID, generatorWrapper);
    return generatorWrapper;
}

from react-native-navigation.

DanielZlotin commented on May 14, 2024 2

I agree @smooJitter . I think changing the API to require a factory method instead of a screenID would be better, and MUCH more flexible (instead me creating the Screen, you create it for me - the way you want).

from react-native-navigation.

explorigin commented on May 14, 2024

I'm working through this. Merely exposing it is not good enough. Currently getting a message: