Explore tweets tagged as #NavigationOptions
I've made a useEventEmitter @reactjs hook to be used with @reactnavigation navigationOptions so you can easily add actions to navigation buttons https://t.co/9R1FcejdsJ
0
2
18
@Baconbrix This API of adding navigationOptions as a static property to screen components is exactly what I'm doing with Next.js pages: https://t.co/PkQbTpyGkF Auto navigation for native is the only missing piece. I can't wait to use this.
0
1
13
How can I pass a function to a header button in react navigation's navigationOptions? https://t.co/OU16Mr82CP
0
0
0
How can I implement a ThemedHeader extending from default Header component in react-navigation? I'm already tried something like this and passing the component as header in navigationOptions, but no success @satya164 @notbrent @reactnavigation
2
0
0
RN + Hooks, navigationOptions fire component's function but with an old value of a the state (the value at the props.navigation.setParams time), any idea how can we fix this?
1
0
1
How to Optimize Your Website for Better User Experience #UserExperience #WebsiteOptimization #WebDesign #EngagementBoost #ConversionTips #WebsiteAnalysis #UXDesign #DigitalMarketing #NavigationOptions #HiddenFeatures
0
0
0
You can disable that behavior by simply adding in the Screen navigationOptions: gesturesEnabled: false boolean. That simple trick will disable all the gestures on that particular screen for you. #reactnative #javascript
1
1
0
@notbrent @EricVicenti Also the upgrade from v2->v3 is really straight-forward. The only two things I had to do are: - export using createAppContainer at the root - update navigationOptions -> defaultNavigationOptions 💯 great job!
0
0
2
This #gist on #github shows a working type definition for navigationOptions for your screens when using #Typescript with #react and #reactnavigation. Hope that helps, finding the correct typings for some libraries is just a pain in the ass. https://t.co/PI7JTfq54j
0
0
1
@jlmmysharpv @davidpaulsson We're haven't updated the docs yet. But you can specify transitions in `navigationOptions`:
0
0
0
@satya164 @notbrent Yah, actually I don't need to inject the event in navigationOptions so I should be fine with context, but interested in a solution where I need a StackNav with title = https://t.co/O8BZ3wVXDN for example
0
0
1
@theluk246 @FezVrasta @reactnative @expo what's inconsistent? can you elaborate on what you mean about navigationOptions getting different? how would you change things?
0
0
0
react-navigation navigationOptions: 1. handle on a class by class basis within component 2. handle all within AppNavigator pros ? cons?
2
1
2
@acemarke "Solved", Internet bro. In a scenario, I was bad person, I didn't map the #Redux store and, of course, it complicated my life. Don't ask. In the other, I have not been able to avoid subscribing to the store since I use the static function navigationOptions of #ReactNavigation v1.
0
1
0
@SeniorFreelance @cmartinjr @expo @Wix i think a lot of this is just inherent complexity of having an app with so many different types of navigation. in the case of not being able to override some of the config in navigationOptions, i'd be curious which ones you've found problematic in particular
1
0
0
@brunocrpontes @notbrent @reactnavigation static navigationOptions = { header: props => <CustomHeader {...props} /> }
2
0
1
is there a hook for static navigationOptions on @reactnavigation ? what is the best practice to avoid using classes just for this static field?
3
0
2