Kevin Ross

I suggest 'app-ruby-config' 'app' is a simple name, but too simple to be descriptive and attract a bigger community.

Problem identified: I expected the `spreadShape` I get from `convertToPropTypes()` to have `properties` that I then flatten and return. On an imported libdef type the `spreadShape` is `raw`, and doesn't...

@brigand I see this marked in code as a `runtime merge`, should this situation be treated like `shape-intersect-runtime`?

@mhaas - which test code is best for me to look at for this runtime intersection from a libdef?

This seems like a strange situation, as I need to **alter** the imported named type by obtaining the properties only (and in cases that don't use `$Exact`, modify the value...

Any `es5` runtime will have none of the definitions found in a local libdef, meaning anything a user types themselves for an external library, or everything from the `flow-typed` project....

I saw the commentary on inlining types and solving the react-docgen problem, which is also a problem for me. I'm going to try out that new plugin and see where...

@mhaas we should be able to interpret flow types from `flow-typed` (or other local libdefs) and create the equivalent prop-types, and this must be done at transpile-time.

`flow-typed`, which effectively is just another local libdef, is not available at `runtime`...that is if you are referring to `runtime` as a browser. `runtime` would need to be on that...

@mhaas [here is a `found` libdef](https://gist.github.com/rosskevin/0a7e854ccc5cb126cd4410c7e1348000). It seems with object type spreads in particular, we really don't have a workaround for imported types, which is a huge problem for me...