Ross Solomon

For example, the material-ui library uses the `withStyles` HoC for most components. This HoC modifies the exported component's properties. For example: https://github.com/mui-org/material-ui/blob/v1-beta/src/Menu/MenuItem.js The component itself takes in `Props` and `ProvidedProps`,...

That's correct in that scenario, though usually I've been using the props for compositions. Ex: ``` import MenuItem from 'whatever'; type Props = React.ElementProps & { foo: string, }; const...

I don't have any more insight, but I've observed similar issues when exporting a generic type modifier that uses `$ObjMap`. I see a handful of open issues talking about issues...

FWIW, I've found that the best approach to Flow is to do things "the flow way." Sometimes that means having to forego standards to appease the sometimes admittedly limited type...

Set the `ignoreAttrs` parser option to `true`. Something like: ```javascript import { parseStringPromise } from 'xml2js'; ... const rawXml = /* ... your raw XML */ const parsed = await...

This fork of GaryCourt's JSV manually converts all relevant commonJS modules to requireJS modules. Everything should continue to work like normal, except that schema definitions must now be explicitly imported...

`format` documentation just seems totally wrong. `DDD` doesn't do what it says, `DDDo` throws `RangeError: Format string contains an unescaped latin alphabet character \`o\``.