tjhintz/foundations-high-performance-react
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixing notes.

Browse Source
This commit is contained in:
Thomas Hintz
2020-10-06 08:23:04 -07:00
parent ba4f38c5a8
commit dbda3e9756
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
foundations-high-performance-react.org
View File

@@ -362,10 +362,10 @@ the pseudocode until we have our own fully functional ~render~ method
using the same general algorithm React uses. In our first pass we will using the same general algorithm React uses. In our first pass we will
focus on the initial render and ignore reconciliation. focus on the initial render and ignore reconciliation.
#+BEGIN_NOTE #+begin_note
Reconciliation is basically React's "diffing" algorithm. We will be Reconciliation is basically React's "diffing" algorithm. We will be
exploring it after we work out the initial render. exploring it after we work out the initial render.
#+END_NOTE #+end_note
#+BEGIN_SRC javascript #+BEGIN_SRC javascript
function render(element, container) { function render(element, container) {
@@ -445,11 +445,11 @@ and based on two major components:
In this section we will focus on the first part: differing types. In this section we will focus on the first part: differing types.
#+BEGIN_NOTE #+begin_note
In this book we won't be covering keys in depth but you will see why In this book we won't be covering keys in depth but you will see why
it's very important to follow the guidance from React's documentation it's very important to follow the guidance from React's documentation
that keys be: stable, predictable, and unique. that keys be: stable, predictable, and unique.
#+END_NOTE #+end_note
The approach we will take here is to integrate the heuristics that The approach we will take here is to integrate the heuristics that
React uses into our ~render~ method. Our implementation will be very React uses into our ~render~ method. Our implementation will be very

2
manuscript/reconciliation.markua
View File

@@ -15,7 +15,7 @@ According to the [React documentation](https://reactjs.org/docs/reconciliation.h
In this section we will focus on the first part: differing types. In this section we will focus on the first part: differing types.
> In this book we won't be covering keys in depth but you will see why it's very important to follow the guidance from React's documentation that keys be: stable, predictable, and unique. I> In this book we won't be covering keys in depth but you will see why it's very important to follow the guidance from React's documentation that keys be: stable, predictable, and unique.
The approach we will take here is to integrate the heuristics that React uses into our `render` method. Our implementation will be very similar to how React itself does it and we will discuss React's actual implementation later when we talk about Fibers. The approach we will take here is to integrate the heuristics that React uses into our `render` method. Our implementation will be very similar to how React itself does it and we will discuss React's actual implementation later when we talk about Fibers.

2
manuscript/render.markua
View File

@@ -24,7 +24,7 @@ Our DOM element is created first. Then we set the properties, render children el
Now that we have an idea of what to build we will work on expanding the pseudocode until we have our own fully functional `render` method using the same general algorithm React uses. In our first pass we will focus on the initial render and ignore reconciliation. Now that we have an idea of what to build we will work on expanding the pseudocode until we have our own fully functional `render` method using the same general algorithm React uses. In our first pass we will focus on the initial render and ignore reconciliation.
> Reconciliation is basically React's "diffing" algorithm. We will be exploring it after we work out the initial render. I> Reconciliation is basically React's "diffing" algorithm. We will be exploring it after we work out the initial render.
{format: "javascript"} {format: "javascript"}
``` ```