From 18775d88e47c7e157dbdff54b7b76b10f259677a Mon Sep 17 00:00:00 2001 From: Toru Kobayashi Date: Wed, 30 Nov 2016 00:45:46 +0900 Subject: [PATCH] Remove output field `output` filed has been removed. https://github.com/facebook/react/pull/8406 --- README.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/README.md b/README.md index e272db3..7652d73 100644 --- a/README.md +++ b/README.md @@ -232,19 +232,6 @@ A fiber's alternate is created lazily using a function called `cloneFiber`. Rath You should think of the `alternate` field as an implementation detail, but it pops up often enough in the codebase that it's valuable to discuss it here. -#### `output` - -
-
host component
-
The leaf nodes of a React application. They are specific to the rendering environment (e.g., in a browser app, they are `div`, `span`, etc.). In JSX, they are denoted using lowercase tag names.
-
- -Conceptually, the output of a fiber is the return value of a function. - -Every fiber eventually has output, but output is created only at the leaf nodes by **host components**. The output is then transferred up the tree. - -The output is what is eventually given to the renderer so that it can flush the changes to the rendering environment. It's the renderer's responsibility to define how the output is created and updated. - ## Future sections That's all there is for now, but this document is nowhere near complete. Future sections will describe the algorithms used throughout the lifecycle of an update. Topics to cover include: