James Friend

I took a fair bit of effort to maintain parity between input lines and output lines but I haven't had time to thoroughly test it. Hopefully I'll get to do...

Thanks, I recently noticed this regression (though it seems it was introduced with spread operator) and I'm working on it presently

Looks like this is a regression, previously if you provided something like `# @cjsx deku.dom` it would just work.

It's a pretty simple fix, the correct value just needs to be output here: https://github.com/jsdf/coffee-react-transform/blob/master/src/serialiser.coffee#L105

You could try applying the React.createElement->JSX codemod to the compiled output. See here: https://github.com/reactjs/react-codemod/ On Sun, 21 Feb 2016 at 8:11 PM, Abe Fehr [email protected] wrote: > I'm really in...

A short term solution is to do your indentation like this: ``` coffee render: -> ``` Note that the closing `>` of a tag lines up with the opening `

That's the style of indentation which React uses [in their examples](https://facebook.github.io/react/docs/transferring-props.html#consuming-and-transferring-the-same-prop)

Try to keep your closing brackets in line with your opening ones. I want to remove this limitation in future but it's a big piece of work

[Example](https://jsdf.github.io/coffee-react-transform/?code=PEZvbwogIGNsYXNzTmFtZT0iRm9vIgo%2BCiAgPEJhcgogICAgY2xhc3NOYW1lPSJCYXIiCiAgPgoKICAgIHtleHByfQogIDwvQmFyPgo8L0Zvbz4%3D)

As I haven't implemented source maps yet, the temporary (but long standing) solution was to make sure the input lines had 1 to 1 parity with output lines.