<story><title>React v0.13.0 Beta 1</title><url>http://facebook.github.io/react/blog/2015/01/27/react-v0.13.0-beta-1.html</url><text></text></story><parent_chain><item><author>JonnieCache</author><text>Similarly, I&amp;#x27;m looking for a way to use react with HAML. I just can&amp;#x27;t give it up, I have absolutely no interest in closing my tags ever again.&lt;p&gt;One of the things I like about angular is how it deals with standard HTML. HAML doesn&amp;#x27;t care about its wacky attributes. Whats the best way to achieve this with react? Does the JSX compiler have hooks for preprocessing of any kind?</text></item><item><author>skrebbel</author><text>Nice! I think that if you use vanilla JS (even ES6), the class support adds more hassle than the gains it provides. For example, setting proptypes completely at the bottom of the file seems, well, cumbersome. It&amp;#x27;s a bit like putting a function signature after the function body. From that perspective, using the old React.createClass syntax seems to keep everything together a bit nicer.&lt;p&gt;However, if you want to use e.g. TypeScript with React, than this is a very big thing! Up until now, it was always a bit of a hassle, and with this change, it&amp;#x27;s completely straightforward (especially if you don&amp;#x27;t want JSX). You&amp;#x27;ll also need propTypes less because you can just use TypeScript interfaces for the `props` constructor parameter. Plus, TypeScript already has property initializers and all that, so all the other annoyances that you get when doing this with plain ES6 classes disappear with TypeScript.&lt;p&gt;I&amp;#x27;m currently really considering porting my current project back to TypeScript for this single reason. The bad mix of TypeScript and JSX is what mostly holds me back. I&amp;#x27;d like my view code to be somewhat understandable&amp;#x2F;hackable by designers and JSX really matters there. Any suggestions?</text></item></parent_chain><comment><author>rattray</author><text>It wouldn&amp;#x27;t work with Typescript, but this is what my vanilla CoffeeScript React code looks like:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    div
      className: &amp;#x27;navbar-form&amp;#x27;
      style: 
        backgroundColor: &amp;quot;green&amp;quot;
      ,
      div
        className: &amp;#x27;btn-group&amp;#x27;
        ,
        button
          type: &amp;#x27;button&amp;#x27;
          className: &amp;#x27;btn btn-warning&amp;#x27;
          onClick: @handleDecreaseWpmClick
          ,
          span
            className: &amp;#x27;glyphicon glyphicon-chevron-down&amp;#x27;
        span
          className: &amp;#x27;btn btn-default disabled&amp;#x27;
          ,
          &amp;quot;#{ @props.status.get(&amp;#x27;wpm&amp;#x27;) }&amp;quot;
          span
            className: &amp;#x27;hidden-xs&amp;#x27;
            ,
            &amp;quot; wpm&amp;quot;
        button
          type: &amp;#x27;button&amp;#x27;
          className: &amp;#x27;btn btn-warning&amp;#x27;
          onClick: @handleIncreaseWpmClick
          ,
          span
            className: &amp;#x27;glyphicon glyphicon-chevron-up&amp;#x27;
&lt;/code&gt;&lt;/pre&gt;
(For the curious, &amp;quot;wpm&amp;quot; is short for &amp;quot;words per minute&amp;quot; - this is straight out of my code for &lt;a href=&quot;http://splashreaderapp.com&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;splashreaderapp.com&lt;/a&gt;. More code at &lt;a href=&quot;http://github.com/rattrayalex/splashreaderapp&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;rattrayalex&amp;#x2F;splashreaderapp&lt;/a&gt;)</text></comment>
<story><title>React v0.13.0 Beta 1</title><url>http://facebook.github.io/react/blog/2015/01/27/react-v0.13.0-beta-1.html</url><text></text></story><parent_chain><item><author>JonnieCache</author><text>Similarly, I&amp;#x27;m looking for a way to use react with HAML. I just can&amp;#x27;t give it up, I have absolutely no interest in closing my tags ever again.&lt;p&gt;One of the things I like about angular is how it deals with standard HTML. HAML doesn&amp;#x27;t care about its wacky attributes. Whats the best way to achieve this with react? Does the JSX compiler have hooks for preprocessing of any kind?</text></item><item><author>skrebbel</author><text>Nice! I think that if you use vanilla JS (even ES6), the class support adds more hassle than the gains it provides. For example, setting proptypes completely at the bottom of the file seems, well, cumbersome. It&amp;#x27;s a bit like putting a function signature after the function body. From that perspective, using the old React.createClass syntax seems to keep everything together a bit nicer.&lt;p&gt;However, if you want to use e.g. TypeScript with React, than this is a very big thing! Up until now, it was always a bit of a hassle, and with this change, it&amp;#x27;s completely straightforward (especially if you don&amp;#x27;t want JSX). You&amp;#x27;ll also need propTypes less because you can just use TypeScript interfaces for the `props` constructor parameter. Plus, TypeScript already has property initializers and all that, so all the other annoyances that you get when doing this with plain ES6 classes disappear with TypeScript.&lt;p&gt;I&amp;#x27;m currently really considering porting my current project back to TypeScript for this single reason. The bad mix of TypeScript and JSX is what mostly holds me back. I&amp;#x27;d like my view code to be somewhat understandable&amp;#x2F;hackable by designers and JSX really matters there. Any suggestions?</text></item></parent_chain><comment><author>pea</author><text>Not what you&amp;#x27;re looking for exactly, but you could settle for using Jade? &lt;a href=&quot;https://github.com/duncanbeevers/jade-react&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;duncanbeevers&amp;#x2F;jade-react&lt;/a&gt;</text></comment>