Samuel Susla a1c5e884ef Fix order of calls on Picker ...

Summary:
In previous implementation, `setNativeProps` was called before `render`. These two methods can change value of `selectedIndex` and it matters in which order they arrive in native.

This was fine in Paper because 1st selectedIndex is set from `setNativeProps` with wrong value and then correct value comes from props.

However in Fabric, 1st selectedIndex comes from props (this is the correct one), and 2nd comes from command which has the incorrect value.

changelog: [internal]

Reviewed By: TheSavior

Differential Revision: D18240118

fbshipit-source-id: dca897306d3e858b9175b2f81356c76f5a0f79e2

2019-11-01 12:11:54 -07:00

..

__tests__

Remove redundant props from Picker

2019-10-07 11:34:50 -07:00

AndroidDialogPickerNativeComponent.js

Core: Remove any from calls to requireNativeComponent

2019-10-14 13:53:48 -07:00

AndroidDropdownPickerNativeComponent.js

Core: Remove any from calls to requireNativeComponent

2019-10-14 13:53:48 -07:00

Picker.js

Re-land stack of D17563110: codemod xplat/js

2019-09-25 14:47:02 -07:00

PickerAndroid.android.js

RN: Cleanup PickerAndroid

2019-06-26 10:05:32 -07:00

PickerAndroid.ios.js

Migrate "Libraries" from Haste to standard path-based requires (sans vendor & renderers) (#24749)

2019-05-08 08:48:59 -07:00

PickerIOS.android.js

Move non-license comments out of license header

2019-10-15 20:12:12 -07:00

PickerIOS.ios.js

Fix order of calls on Picker

2019-11-01 12:11:54 -07:00

RCTPickerNativeComponent.js

Tidy up license headers [2/n]

2019-10-16 10:06:34 -07:00