Kevin Ross

Results 30 issues of Kevin Ross

`babel-7` branch - I'm looking into this. `found` is in a local libdef. ```javascript import type {RoutingState} from 'found' type Props = { ...$Exact, classes: Object, children?: Element, currentUser?: CurrentUser,...

I'm using the new types, and getting invalid errors, only when I inline the `type` import. e.g. ``` Warning: Failed prop type: Invalid prop `children` of type `Array` supplied to...

`flow-upgrade` effectively turned weak components into ```javascript class Foo extends React.Component ``` This causes this plugin to fail with: ``` Did not find type annotation for UnmountTransition at annotate (/Users/kross/projects/material-ui/node_modules/babel-plugin-flow-react-proptypes/lib/index.js:89:13)...

Source (mimicing [result of `findDOMNode()`](https://github.com/facebook/flow/blob/v0.49.1/lib/react.js#L244)): ```js /** * return type of ReactDOM.findDOMNode() * * NOTE: `Element` is NOT the same as `type { Element } from 'react'` a.k.a React$Element *...

First, thank you for all the work that went into this. In the recent days I've seen how much time and effort it took to get this right. I don't...

I have built some helper methods to help assemble instances in our common patterns. With the recent introduction of #47, and the fact that none of the `Base` types are...

I have updated the wiki instructions for the moment, advising the manual installation route. If these repositories are not going to be updated, perhaps we should remove those instructions and...

Object type spread was introduced in [Flow 0.42.0](https://github.com/facebook/flow/releases/tag/v0.42.0) _Documentation_ is not yet published, but the [behavior is documented here](https://github.com/facebook/flow/issues/3534#issuecomment-287580240) and this is referenced in the implementation, as use without `$Exact`...

## 🐛 Bug Report A workaround was introduced in https://github.com/i18next/react-i18next/pull/1227 by [pedrodurek](https://github.com/pedrodurek) due to bug https://github.com/i18next/react-i18next/issues/1222 reported by @jigsawye. The underlying issue https://github.com/microsoft/TypeScript/issues/41406 has been fixed. I noticed because we...

typescript