Docs updates per community response #14
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe React and JSX should be split in 2 separate projects, to clarify even further the separation. |
|
@xcambar they definitely are internally, we should look into moving in that direction externally as well. This should be a good start though. |
petehunt
added a commit
that referenced
this pull request
May 30, 2013
Docs updates per community response
| React minimizes interactions with the DOM by using a mock representation | ||
| of the DOM. | ||
| Describe how you want your component to look. React will automatically compute | ||
| the fastest way to keep the UI up-to-date when the data changes. |
There was a problem hiding this comment.
How about "the fastest way to update the UI when the data changes"?
vjeux
added a commit
that referenced
this pull request
Jan 6, 2014
…IE8 … 8615ade philix Add jsx-requirejs-plugin to the tooling-integration page 978a8f5 philix Remove the require-jsx plugin from the tooling-integration page … e23e627 spicyj Mention react-art where we talk about SVG 13c211a spicyj Fix typo 3afe6de passy Add gulp-react to Helpful OSS Projects … 8ef2cec xixixao Document displayName ee90857 Daniel15 Add link to HTML to JSX converter to “JSX In Depth” page 5cbc727 Daniel15 Change “not allowed” back to “discouraged” since you technically *can… … ea41991 vjeux Community Round-up #14 658aa45
georgesisco
added a commit
to georgesisco/react
that referenced
this pull request
Apr 9, 2014
… steps The following steps also have an ajax function, but the 'error:' param is gone after facebook#13: facebook#14 facebook#17 facebook#19 facebook#20 This may be superfluous, but it helped me find an error with something I was doing - Namely, in my .json file, I had single line javascript comments ("//") that I copied from the tutorial. I couldn't find the issue on later steps, but was able to see my issue when the error handler complained about an unexpected "/" in my file in step facebook#13.
zpao
pushed a commit
that referenced
this pull request
May 8, 2014
The following steps also have an ajax function, but the 'error:' param is gone after #13: #14 #17 #19 #20 This may be superfluous, but it helped me find an error with something I was doing - Namely, in my .json file, I had single line javascript comments ("//") that I copied from the tutorial. I couldn't find the issue on later steps, but was able to see my issue when the error handler complained about an unexpected "/" in my file in step #13.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Man, we did a bad job messaging JSX and component architectures in general. This tries to reposition us a little better.
I may beat the JSX horse a little bit, but I think it's one that needs to be beaten.