Async options with Promises - Promise object bug

[VladimirPal]

#940

[coveralls]

Coverage remained the same at 90.909% when pulling 5df5fa2 on VladimirPal:async_promise_bug into b21f70e on JedWatson:master.

[coveralls]

Coverage remained the same at 90.909% when pulling 5df5fa2 on VladimirPal:async_promise_bug into b21f70e on JedWatson:master.

[JedWatson]

@VladimirPal wow, thanks for not just fixing this but adding a compete example! great work 👍

[f2net]

In the /lib folder I still see the old Select.js without this fix. Why?

Thank you,
Matteo Frana

[VladimirPal]

@f2net It's because lib folder builds automatically after releasing new version, looks like you have to build it manually:
cd node_modules/react-select
npm install && npm build

[VladimirPal]

@JedWatson Maybe you can build current state of project or release new version? I think this bug is pretty important

[f2net]

@JedWatson @VladimirPal I agree, I think the current state should be built, otherwise who installs the package via npm without building gets the [Promise object] bug.
Thank you for this great component.

[eliseumds]

May we have a release?

[f2net]

Could you update the /lib version too, since the file in the /lib folder is still bugged?
Every time I distribute an app with react-select async I have to manually change line 390 of Select.js in /lib to:

if (nextState != null && typeof nextState !== 'object') {

Thank you,
Matteo

[jeffreybrowning]

I would love a release.

[khankuan]

@JedWatson any chance of a release soon? :)

[TrevorBurnham]

FYI I've published a release of the react-select-plus with this patch, 1.0.0-beta13.patch1.