Tweak glossary#176
Conversation
|
Deploy preview ready! Built with commit 4b4d307 |
|
Deploy preview ready! Built with commit 189a45d |
bvaughn
left a comment
bvaughn
left a comment
There was a problem hiding this comment.
Looks great, Dan. I left a couple of minor thoughts/suggestions. Feel free to ignore any you don't like.
|
|
||
| ## ES6/ES2015/ES7/ES2016/ES8/ES2017 | ||
| These acronyms all refer to the most recent versions of the ECMAScript Language Specification standard, which the JavaScript language is an implementation of. It includes many additions to the previous versions such as: arrow functions, classes, template literals, `let` and `const` statements. You can learn more about specific versions [here](https://en.wikipedia.org/wiki/ECMAScript#Versions). | ||
| Though you may build a single-page application in React, it is not a requirement. React can also be used for enhancing small parts of existing websites with additional interactivity. Code written in React can coexist peacefully with markup rendered on the server by something like PHP, or with other client-side libraries. In fact, it's exactly how React is being used at Facebook. |
There was a problem hiding this comment.
nit suggestion:
In fact, this is exactly how React is being used at Facebook.
|
|
||
| ## [Elements](/docs/rendering-elements.html) | ||
|
|
||
| React elements are the building blocks of React applications. One might confuse elements with a more widely known concept of "components". Elements are what components are "made of". An element describes what you want to see on the screen. React elements are immutable. |
There was a problem hiding this comment.
I still think the wording here is a bit vague:
Elements are what components are "made of".
I wonder if we could improve it by changing it to something like:
Elements are a template for creating components.
There was a problem hiding this comment.
I just removed this sentence since it's duplicating the same thought as in first sentence and then after the snippet.
| return <p>{this.props.children}</p>; | ||
| } | ||
| } | ||
| ``` |
| An input form element whose value is controlled by React is called a *controlled component*. When a user enters data into a controlled component a change event handler is triggered and your code decides whether the input is valid (by re-rendering with the updated value). If you do not re-render then the form element will remain unchanged. | ||
|
|
||
| An *uncontrolled component* works like form elements do outside of React. When a user inputs data into a form field (an input box, dropdown, etc) the updated information is reflected without React needing to do anything. | ||
| An *uncontrolled component* works like form elements do outside of React. When a user inputs data into a form field (an input box, dropdown, etc) the updated information is reflected without React needing to do anything, but you can't force the field to have a certain value. |
There was a problem hiding this comment.
nit suggestion:
When a user inputs data into a form field (an input box, dropdown, etc) the updated information is reflected without React needing to do anything. This also means that you can't force the field to have a certain value.
* Translated "Community/Conferences"; * Update error in line 13. * update error in line 11.
4 participants
Just rewriting a little bit more to my liking.