Set default params?

[j-mendez]

Is there any way to set a default param on the component itself?

[grabbou]

See https://reactnavigation.org/docs/navigators/navigation-options, section Default parameters

[j-mendez]

@grabbou I do not see this section.

[grabbou]

Try Default navigation options 😊

[j-mendez]

@grabbou static navigationOptions = { state: { params: { something: false, somethingElse: false } } } did not work.

[grabbou]

Ah, sorry. I thought you were talking about navigation options (and its default values). Do you mean default parameters for a scene? Can you post a simple code to demonstrate what you want to achieve? That would help me understand it a bit more.

…

On Wed, Feb 22, 2017, 18:19 Jeff Mendez ***@***.***> wrote: @grabbou <https://github.com/grabbou> static navigationOptions = { state: { params: { something: false, somethingElse: false } } } did not work. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#441 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACWcxqcFc4A1kjXT2gy_0GzuRZjjaem_ks5rfG4wgaJpZM4MI4gp> .

[j-mendez]

@grabbou Sure. I want to achieve this but for navigation state params since I have a statement checking to see if the prop has been passed down and set to true and need to default it to false.

[j-mendez]

I would like to be able to set this default value of popToStart for instance.

[ddeanto]

This may be related to #232

[grabbou]

@jeffreymendez1993 why wouldn't const value = params.popToStart || 'defaultValue'; work?

[j-mendez]

@grabbou It would work, but wouldn't you want to be able to setDefault params just how you setDefault props to have a clear vision on what the default to certain things would be. If not I guess that would work for now.

[thurt]

as far as I'm aware, you currently cannot set default parameters for a scene/screen. but seems like there is a good argument for adding them

[j-mendez]

@thurt I think this should be added as for this makes code clean and easy to read.

[dantman]

This is especially important for things like the DrawerNavigator where routes are not opened by a navigator.navigate(..., params) call within the app, but instead are navigated to by the DrawerRouter without any params.

Without default params it's not possible (at least not without fudging things using the routeName) to have a bunch of drawer items with the same screen but different params, like:

DrawerNavigator({
  Inbox: {
    screen: MessageList,
    params: {
      filter: {
        archived: false
      }
    },
  },
  Archives: {
    screen: MessageList,
    params: {
      filter: {
        archived: true
      }
    },
  },
  AllMessages: {
    screen: MessageList,
  },
});

[j-mendez]

@dantman that would be perfect

[ntkzwane]

I share the same sentiments with @dantman, except my scenario involves use of the TabNavigator. I see you made reference to #838, however this wouldn't be the cleanest solution in my opinion.

[0x5e]

Same problems with @dantman . Same screen with different params.

[jiyarong]

Has the problem been solved?

[brentvatne]

hi there! I moved this feature request to canny, as it's our new home for feature requests: https://react-navigation.canny.io/feature-requests/p/set-default-params-in-a-screen-component

issues are now only for bugs

[brentvatne]

where you use the param, you can do this:

this.props.navigation.getParam('name', defaultValueHere)

if you think this api isn't good enough then please open a rfc to discuss further

[brentvatne]

the api that @dantman suggested above was implemented in react-navigation/core#11