* Clarify language in components-and-props.md
This is a nit for a few reasons:
- The point that extracting a component that "is complex enough on its own" means that it's not necessarily reusable.
- Extracting the components listed in the same sentence (e.g. App) are not necessarily reusable.
- This ends the section "Extracting Components" with a reference to extraction instead of re-usability.
- This delimits extracting into a separate component from creating a re-usable component.
* Update components-and-props.md
* Update components-and-props.md
This is a very basic app but useful to understand the React Components, states, Data Flow, parent to child etc. .
Co-authored-by: Dan Abramov <dan.abramov@gmail.com>
* Add ajax with hooks example
* Add comment about empty deps in useEffect hook
* grammar
Co-authored-by: Alex Krolick <alexkrolick@users.noreply.github.com>
Having the information that the plugin is already installed by default after the installation instructions is probably wasting a lot of people's time. Moving it up probably avoids multiple installs of the plugin.
* Clarify preferred "props default to true" expr
The current text is ambiguous without reading further into the paragraph -- until I re-read this text, I was trying to avoid both types of syntax because it seemed to imply that it wans't recommended (eg "props default to true" --> "we don't recommend using this").
* Update jsx-in-depth.md
Co-authored-by: Sunil Pai <threepointone@oculus.com>
The ternary syntax using parenthesis was an unconventional prettier invention, going out of its way to format react ternaries differently from normal ternaries (if i remember correctly, because vim users had trouble re-formating without a mouse). If they made the right decision or not is one thing, but the additional noise could mislead beginners here, thinking they have to add more characters to make a simple 2-slot ternary, or that it is a "react thing".