react.dev

Author	SHA1	Message	Date
Max	f31c84e765	Update documentation to stateless components Ref #5949 @jimfb	9 years ago
Martin Hujer	8f952eecd6	Transform rest and spread properties using Babel 6 > Out of the box Babel doesn't do anything. In order to actually do > anything to your code you need to enable plugins. > (https://babeljs.io/docs/plugins/)	9 years ago
Martin Hujer	981d6d0814	Rest/Spread Properties may not be part of ES7 According to the http://www.2ality.com/2015/11/tc39-process.html it is not a good idea to guess target ES version until the proposal reaches later phases. Even the proposal repository now states > It is a Stage 2 proposal for ECMAScript. < (it has been changed in `e9813ac78a`)	9 years ago
Jim	33cd980f0e	React -> ReactDOM for render() and findDOMNode()	9 years ago
Paul O’Shannessy	6d0dba5458	[docs] Remove mentions of react-tools/jsx command	9 years ago
Leon Yip	6baacdcde6	Update 06-transferring-props.md "This ensures that" sounds a better than "That ensures that." This change is just my personal opinion, so I totally understand my change doesn't get merged.	10 years ago
Tsung Hung	04fac68f10	updated some typos, grammers, and made sentences sound better	10 years ago
Reed Loden	dd010b34e2	SSL/TLSize all the things! (convert http:// to https:// where appropriate) Update links to use https:// where it is supported. There's probably a lot more that could be fixed, but these are the core ones I found (especially the download links in order to prevent MITM attacks). Note that there are some fb.me links that will redirect to http:// even while accessed over https://, but this seemed like the best way to fix those for now. NOTE: Only non-third-party files were modified. There are references to http:// URLs in vendored/third-party files, but seems appropriate to fix upstream for those rather than editing the files. Also, copy one image locally to the blog, as it was hotlinking to a site that did not support https://. Last, use youtube-nocookie.com instead of youtube.com for video embeds, as the former doesn't try to set a cookie on load (privacy enhancement).	10 years ago
David Mininger	84c3212a78	Docs: Fix example JSX output	10 years ago
Julen Ruiz Aizpuru	3ebec4b55b	Docs: do not render components to `document.body` Rendering to `document.body` in the examples is conveniently short, but it can be misleading at the same time, especially for newcomers. While it's possible to render React components to `document.body`, any 3rd party scripts can also mess up with it, and it can have unintended consequences and be source of difficult-to-trace bugs.	10 years ago
Patrick Laughlin	d1eda2cb43	Update 06-transferring-props.md	10 years ago
Kirk Steven Hansen	de43169c6b	Typo in first commit.	10 years ago
Kirk Steven Hansen	e4d4cd3e59	Updated tutorial to be more clear about the dependence on the --harmony flag.	10 years ago
cookfront	83d5a4514d	The same problem in issue #2648	10 years ago
张敏	e693d3f321	In `Transferring Props` guide, `Manual Transfer` section will lead an error ```c var FancyCheckbox = React.createClass({ render: function() { var fancyClass = this.props.checked ? 'FancyChecked' : 'FancyUnchecked'; return ( <div className={fancyClass} onClick={this.props.onClick}> {this.props.children} </div> ); } }); React.render( <FancyCheckbox checked={true} onClick={console.log}> Hello world! </FancyCheckbox>, document.body ); ``` When click `Hello world!` will lead a `Uncaught TypeError: Illegal invocation` error	10 years ago
Stefan Dombrowski	26ad3053c5	React.renderComponent --> React.render Also fixed a spelling mistake.	10 years ago
Sebastian Markbage	4202fcd9c5	Replace transferPropsTo with transferring props patterns	10 years ago

18 Commits (a9e07a8b3c36eb49e5da3c88e8a7895591303a37)