Skip to content

Conversation

@stam
Copy link
Contributor

@stam stam commented Jun 28, 2016

This allows the NavigationCard style to be extended, the default backgroundColor style of the NavigationCard is not applicable to all apps.
Fixes issue #8116. PR #8115 was already made for this but didn't pass CI checks.

Test plan

When rendering a NavigationCardStack, add

const { CardStack } = NavigationExperimental;
...

<CardStack cardStyle={{ backgroundColor: 'purple' }} />

to see that the NavigationCard background has changed to purple.

This allows the NavigationCard style to be extended, the default
backgroundColor style is not applicable to all apps.
Fixes issue facebook#8116. PR facebook#8115 was already made for this but didn't pass
the CI checks.
@ghost
Copy link

ghost commented Jun 28, 2016

By analyzing the blame information on this pull request, we identified @hedgerwang and @jmurzy to be potential reviewers.

@ghost
Copy link

ghost commented Jun 28, 2016

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at [email protected]. Thanks!

@stam
Copy link
Contributor Author

stam commented Jun 28, 2016

Closing, because CLA doesn't seem to work from my organization.

@stam stam closed this Jun 28, 2016
key={'card_' + props.scene.key}
panHandlers={panHandlers}
renderScene={this.props.renderScene}
style={style}

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

property cardStyle Property not found in object type

@lgan1989
Copy link
Contributor

lgan1989 commented Sep 8, 2016

The propType check in NavigationCard for style is Proptypes.any.

While in NavigationCardStack, the cardStyle is validated as View.propTypes.style.

It's better to keep the type consistent to avoid unnecessary warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants