-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[UIExplorer] Update SegmentedControlIOSExample.js #1453
Conversation
for event.nativeEvent ,the selectedIndex,can't work. issues is here: <a href="https://github.com/facebook/react-native/issues/1310">https://github.com/facebook/react-native/issues/1310</a>
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 cla@fb.com. Thanks! |
</Text> | ||
<SegmentedControlIOS | ||
values={this.state.values} | ||
selectedIndex={this.state.selectedIndex} | ||
selectedSegmentIndex={this.state.selectedSegmentIndex} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strangely enough, the prop name is actually segmentedIndex
. Maybe we should change this so it is consistent on both ends.
Any updates on this? |
@donghanji updated the pull request. |
Bump lodash.merge from 4.6.1 to 4.6.2 in /website
…names [0.68-stable] A couple of renames to make Dynamic Type features more proper
for event.nativeEvent ,the selectedIndex,can't work.
issues is here:
#1310