* moved existing "react-select" definitions into "v1" directory
* updated references to V1 of "react-select"
* dts-gen --dt --name react-select --template module
* added placeholders for react-select definitions and tests
* fixed imports of react and react-select
* updated config. files
* drafted definitions for react-select
* updated definitions for react-select
* made Props in stateManager.d.ts and Select.d.ts optional
* handle grouped options in Select.d.ts
* updated definitions for react-select
* resolved merge conflicts
* fixed issues identified by "npm test"
* updated type of "menuPortalTarget"
* remove OptionType type and introduce throughout as a generic parameter
* add an extra type
* re-enable interface-over-type-literal lint rule
* parameterize GroupedOptionsType
after some consideration this should be parameterized, typically with a union type, see Grouped example which is a select of `ColourOption | FlavourOption`
* typing as per https://github.com/plotly/react-plotly.js/issues/80
* fix travis build (thanks intellij...)
* bring typescript version inline with react
* types for react-flag-icon-css
* review feedback, remove react-plotly.js changes from PR as already released
* attempt to fix travis
* life is too short to argue about this nonsense, switch spaces for tabs if you want
* Fix InferableComponentEnhancerWithProps type inference for StatelessComponent
The inferred component should require the difference of props supplied by connect
and props needed by the component to be passed during render.
* Remove ambigous bidirectional type inference
* Adding definations for fastGet, fastPut in ssh2-sftp-client
* Adding proper ssh2-streams typing for ssh2-sftp-client functions fastGet and fastPut
* Adding type for return value of fastGet and fastPut
* Lodash: `fp.pickBy`: add failing type guard test
* Lodash: `fp.pickBy`: use generic for property value instead of generic to fix FP test
* Lodash: update generated typings
* Lodash: `fp.pickBy`: add overload for user-defined type guard with `NumericDictionary`
* Lodash: update generated typings
* Correct `predicate` type of `pickBy`
* Lodash: update generated typings
* Rename `ObjectIteratorTypeGuardWithoutCollection` to `ValueKeyIterateeTypeGuard`
* Lodash: update generated typings
* Constant `userDefinedTypeGuard`
The documentation gets weird about the API promising to return *some* kind
of value that evaluates to false, even if that might be the number zero.
The original types author expressed that as CouchbaseError | number, but
that makes it seem like the result could be some non-zero number.
I don't know whether the library actually issues callback(0) calls, but to
make it play better with normal callbacks (err?: Error), we will act as if
it uses null instead of zero.
Nikolai Ommundsen