From cd2ff2e884f1fedbd2ac031ee48e5d5d350324d2 Mon Sep 17 00:00:00 2001 From: Israel Shmueli Date: Sun, 2 Sep 2018 23:35:51 +0300 Subject: [PATCH] Fix broken link in documentaion inside element/README.md, broken link points to blocks/README.md##example (#9552) --- packages/element/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) mode change 100644 => 100755 packages/element/README.md diff --git a/packages/element/README.md b/packages/element/README.md old mode 100644 new mode 100755 index ebed8737e8c1be..32bec12c1218fe --- a/packages/element/README.md +++ b/packages/element/README.md @@ -47,7 +47,7 @@ Refer to the [official React Quick Start guide](https://reactjs.org/docs/hello-w At the risk of igniting debate surrounding any single "best" front-end framework, the choice to use any tool should be motivated specifically to serve the requirements of the system. In modeling the concept of a [block](../../blocks/README.md), we observe the following technical requirements: -- An understanding of a block in terms of its underlying values (in the [random image example](../../blocks/README.md#example), a category) +- An understanding of a block in terms of its underlying values (in the [random image example](../blocks/README.md#example), a category) - A means to describe the UI of a block given these values At its most basic, React provides a simple input / output mechanism. __Given a set of inputs ("props"), a developer describes the output to be shown on the page.__ This is most elegantly observed in its [function components](https://reactjs.org/docs/components-and-props.html#functional-and-class-components). React serves the role of reconciling the desired output with the current state of the page.