Closed johnjbarton closed 8 years ago
This is a bug in the parser. The way it works now is that the scanner has scanJsx/peekJs and that ends up treating this
as a JsxIdentifier
which leads to this bug. I think I should refactor the parser for jsx to work more like how we parse template strings with. The downside is that it introduces "a lot" of new AST nodes:
>text<
>text{
}text{
}text<
I tried an example from https://facebook.github.io/react/docs/reusable-components.html#es6-classes
But the fails on
Unexpected token this
. To be sure I don't know JSX. Any hints?