Fixing notes.
This commit is contained in:
@@ -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 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.
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
> 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"}
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user