From a8e5cc424f7d798b101584fa55bdb406ff213856 Mon Sep 17 00:00:00 2001 From: Leigh Halliday Date: Thu, 25 Oct 2018 12:59:31 -0400 Subject: [PATCH 1/8] Fixing a small grammer mistake on the code-splitting page --- content/docs/code-splitting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/code-splitting.md b/content/docs/code-splitting.md index 132fa99a4..091ea3dd8 100644 --- a/content/docs/code-splitting.md +++ b/content/docs/code-splitting.md @@ -117,7 +117,7 @@ parse the dynamic import syntax but is not transforming it. For that you will ne > > `React.lazy` and Suspense is not yet available for server-side rendering. If you want to do code-splitting in a server rendered app, we still recommend [React Loadable](https://github.com/thejameskyle/react-loadable). It has a nice [guide for bundle splitting with server-side rendering](https://github.com/thejameskyle/react-loadable#------------server-side-rendering). -The `React.lazy` function lets you render an dynamic import as a regular component. +The `React.lazy` function lets you render a dynamic import as a regular component. **Before:** From 451a96c311f145aea332d17585e5ec2425332474 Mon Sep 17 00:00:00 2001 From: Misha Moroshko Date: Fri, 26 Oct 2018 16:18:29 -0700 Subject: [PATCH 2/8] Tip => Note "Tip" usually contains an action for you to perform. "Note" is more appropriate here since it's just an FYI. --- content/docs/hooks-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/hooks-faq.md b/content/docs/hooks-faq.md index ca01054c1..89c0da712 100644 --- a/content/docs/hooks-faq.md +++ b/content/docs/hooks-faq.md @@ -396,7 +396,7 @@ In large component trees, an alternative we recommend is to pass down a `dispatc const TodosDispatch = React.createContext(null); function TodosApp() { - // Tip: `dispatch` won't change between re-renders + // Note: `dispatch` won't change between re-renders const [todos, dispatch] = useReducer(todosReducer); return ( From 9e9647c8a196b598477fa45357cd6a9ece6e482c Mon Sep 17 00:00:00 2001 From: Narin Luangrath Date: Fri, 11 Jan 2019 11:03:04 -0800 Subject: [PATCH 3/8] Fix typo in profiler-readme `aso` -> `also` --- content/blog/2018-09-10-introducing-the-react-profiler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2018-09-10-introducing-the-react-profiler.md b/content/blog/2018-09-10-introducing-the-react-profiler.md index d73131fcb..47211d370 100644 --- a/content/blog/2018-09-10-introducing-the-react-profiler.md +++ b/content/blog/2018-09-10-introducing-the-react-profiler.md @@ -140,7 +140,7 @@ It also shows that each time it rendered, it was the most "expensive" component To view this chart, either double-click on a component _or_ select a component and click on the blue bar chart icon in the right detail pane. You can return to the previous chart by clicking the "x" button in the right detail pane. -You can aso double click on a particular bar to view more information about that commit. +You can also double click on a particular bar to view more information about that commit. ![How to view all renders for a specific component](../images/blog/introducing-the-react-profiler/see-all-commits-for-a-fiber.gif) From dfaa41deabada361a0f93c7f58a50931a8a33fd5 Mon Sep 17 00:00:00 2001 From: evolveris Date: Sat, 19 Jan 2019 11:43:17 +0000 Subject: [PATCH 4/8] Fix typo --- content/docs/strict-mode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/strict-mode.md b/content/docs/strict-mode.md index 09b3b9e5d..889490b5e 100644 --- a/content/docs/strict-mode.md +++ b/content/docs/strict-mode.md @@ -57,7 +57,7 @@ React used to support `findDOMNode` to search the tree for a DOM node given a cl `findDOMNode` can also be used on class components but this was breaking abstraction levels by allowing a parent to demand that certain children was rendered. It creates a refactoring hazard where you can't change the implementation details of a component because a parent might be reaching into its DOM node. `findDOMNode` only returns the first child, but with the use of Fragments, it is possible for a component to render multiple DOM nodes. `findDOMNode` is a one time read API. It only gave you an answer when you asked for it. If a child component renders a different node, there is no way to handle this change. Therefore `findDOMNode` only worked if components always return a single DOM node that never changes. -You can instead make this explicit by pass a ref to your custom component and pass that along to the DOM using [ref forwarding](/docs/forwarding-refs.html#forwarding-refs-to-dom-components). +You can instead make this explicit by passing a ref to your custom component and pass that along to the DOM using [ref forwarding](/docs/forwarding-refs.html#forwarding-refs-to-dom-components). You can also add a wrapper DOM node in your component and attach a ref directly to it. From a9989290aaaf7858d7c2d6ccf8c8e7948c60b33b Mon Sep 17 00:00:00 2001 From: Joe Maddalone Date: Wed, 20 Feb 2019 07:49:09 -0600 Subject: [PATCH 5/8] Add React Loop 2019 (#1693) --- content/community/conferences.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/community/conferences.md b/content/community/conferences.md index c10cdb607..a9e3694f7 100644 --- a/content/community/conferences.md +++ b/content/community/conferences.md @@ -41,6 +41,11 @@ June 12, 2019. Larvik, Norway [Website](https://reactnorway.com) - [Twitter](https://twitter.com/ReactNorway) +### React Loop 2019 {#react-loop-2019} +June 21, 2019 Chicago, Illinois USA + +[Website](https://reactloop.com) - [Twitter](https://twitter.com/ReactLoop) + ### ComponentsConf 2019 {#componentsconf-2019} September 6, 2019 in Melbourne, Australia [Website](https://www.componentsconf.com.au/) - [Twitter](https://twitter.com/componentsconf) From e5a97f2d7e2af8ef6ff2a0559790fb85aa7955b7 Mon Sep 17 00:00:00 2001 From: Varser Zakaryan <37110358+varszakaryan@users.noreply.github.com> Date: Wed, 20 Feb 2019 17:49:38 +0400 Subject: [PATCH 6/8] Add React Conf Armenia 2019 to conferences (#1715) This is the first React Conf in the region and it is going to be cool. --- content/community/conferences.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/community/conferences.md b/content/community/conferences.md index a9e3694f7..62ac39b40 100644 --- a/content/community/conferences.md +++ b/content/community/conferences.md @@ -36,6 +36,11 @@ May 23-24, 2019 in Paris, France [Website](https://www.react-europe.org) - [Twitter](https://twitter.com/ReactEurope) - [Facebook](https://www.facebook.com/ReactEurope) - [Videos](https://www.youtube.com/c/ReacteuropeOrgConf) +### React Conf Armenia 2019 {#react-conf-am-19} +May 25, 2019 in Yerevan, Armenia + +[Website](https://reactconf.am/) - [Twitter](https://twitter.com/ReactConfAM) - [Facebook](https://www.facebook.com/reactconf.am/) - [YouTube](https://www.youtube.com/c/JavaScriptConferenceArmenia) - [CFP](http://bit.ly/speakReact) + ### React Norway 2019 {#react-norway-2019} June 12, 2019. Larvik, Norway From 7b5f4cf604f2d6c650b675f59fa1e34395aa995b Mon Sep 17 00:00:00 2001 From: David Svetlecic Date: Wed, 20 Feb 2019 16:38:42 -0600 Subject: [PATCH 7/8] Add 'you' --- content/docs/hooks-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/hooks-faq.md b/content/docs/hooks-faq.md index 524c7068f..25e00c2ef 100644 --- a/content/docs/hooks-faq.md +++ b/content/docs/hooks-faq.md @@ -466,7 +466,7 @@ Note that this approach won't work in a loop because Hook calls [can't](/docs/ho ### How to create expensive objects lazily? {#how-to-create-expensive-objects-lazily} -`useMemo` lets you [memoize an expensive calculation](#how-to-memoize-calculations) if the inputs are the same. However, it only serves as a hint, and doesn't *guarantee* the computation won't re-run. But sometimes need to be sure an object is only created once. +`useMemo` lets you [memoize an expensive calculation](#how-to-memoize-calculations) if the inputs are the same. However, it only serves as a hint, and doesn't *guarantee* the computation won't re-run. But sometimes you need to be sure an object is only created once. **The first common use case is when creating the initial state is expensive:** From a5ad51c60ca4c7d2e22a2077199b36c3cc888c42 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rainer=20Mart=C3=ADnez=20Fraga?= Date: Wed, 20 Feb 2019 21:12:57 -0500 Subject: [PATCH 8/8] Update strict-mode.md --- content/docs/strict-mode.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/docs/strict-mode.md b/content/docs/strict-mode.md index 6618d19af..7e2ba0ac6 100644 --- a/content/docs/strict-mode.md +++ b/content/docs/strict-mode.md @@ -57,11 +57,7 @@ React solía soportar `findDOMNode` para buscar en el árbol un nodo del DOM dad `findDOMNode`también puede ser utilizado en componentes con clases pero esto estaba dañando los niveles de abstracción al permitir a un padre solicitar que cierto hijo fuera renderizado. Esto crea un peligro para refactorizar algo en el caso que no puedas cambiar los detalles de la implementación de un componente ya que un padre puede estar utilizando uno de sus nodos del DOM. `findDOMNode` sólo retorna el primer hijo, pero con el uso de los Fragmentos, es posible que un componente pueda renderizar múltiples nodos del DOM. `findDOMNode` es una API de solo lectura para usar una sola vez. Sólo da una respuesta cuando se invoca el método. Si un componente hijo renderiza un nodo diferente, no hay forma alguna de manipular este cambio. Por lo tanto `findDOMNode` solo funciona si los componentes simpre retornan un solo nodo de DOM que nunca cambie. -<<<<<<< HEAD En su lugar puedes hacer que este comportamiento sea explicito pasando un ref a tu componente personalizado y transmitiéndolo al DOM usando el [reenvío de ref](/docs/forwarding-refs.html#forwarding-refs-to-dom-components). -======= -You can instead make this explicit by passing a ref to your custom component and pass that along to the DOM using [ref forwarding](/docs/forwarding-refs.html#forwarding-refs-to-dom-components). ->>>>>>> 21ca8ed58819b9b498d8c55066e1e299c9dbe452 También puedes agregar un nodo del DOM envuelto en tu componente y vincular un ref directamente al mismo.