Kevin Barabash

Does this handle lifecycle methods that take `props`?

It might make sense to have a separate core-dom report for DOM related polyfills. I say this after having requested `NodeList[Symbol.iterator]` be added a while back. I think the reason...

I ran into some issues when running this on my code so there's at least one edge case I haven't handle. For some of the code I get a parse...

It turns out I was clone too soon and sometimes `props` would be a function instead of an object. I've move the clone operation to be right before where the...

~I think this is an issue with the babel plugins/presets I have configured. I'm trying to make my setup match the setup used in the tests.~

It turns out it wasn't a configuration issue, but rather an issue when there are multiple components in the same file while using imported types. I'll try to create a...

Splitting up the files did indeed solve the issue.

Disabling the `@babel/env` preset in the test outputs the following code which has no undefined variables: ``` // Jest Snapshot v1, https://goo.gl/fbAQLP exports[`import-object 1`] = ` "function _defineProperty(obj, key, value)...

Answering my own question about the stay, you do the following: ``` solver.addEditVar(stayVar); solver.suggestValue(stayVar, newValue); solver.resolve(); ```

Unfortunately, the language I'm parsing is a variation on TypeScript and supports JSX (and template literal strings). Both of these things (JSX probably more so) make it really difficult to...