Kevin Barabash

Right now this has to be removed manually.

Right now PropTypes.node gets converted to `string | null | React.Element | ...`. Using `React.Node` would result in cleaner output.

Are there any breaking changes between v1 and v2?

I experienced this in https://www.joshwcomeau.com/posts/dynamic-bezier-curves#bezier-curves-in-react.

Fix #215

3

In some situations where imported prop types were being used in multiple components, some of the AST nodes generated by the plugin were being used in multiple places which caused...

The following code: ``` type NestedArray = (T | NestedArray)[]; export type Props = { numbers: NestedArray, }; ``` produces the following error: ``` RangeError: Maximum call stack size exceeded...

The following code: ``` type MyType = Array; export type Props = { numbers: MyType, }; ``` results in the following error: ``` TypeError: internalTypes[node.id.name] is not a function 49...

Undefined variable in output when input file contains two classes using same prop types

4

Example code: ``` import * as React from "react"; import type {RowProps} from "./other-row.jsx"; type StaticProps = RowProps & { domain: string, }; class TableOfContentsRow extends React.Component { render() {...

making it easier to debug

1

I was trying to figure out how to update the value of a stay so I thought I'd require the `../cassowary/src/c.js` or `../cassowary/index.js`. I added cassowary.js as a submodule and...

It would be nice to be able to see the combinations in a grid/table.