summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGeorgios Andreadis <g.andreadis@student.tudelft.nl>2017-09-28 14:14:13 +0200
committerGeorgios Andreadis <g.andreadis@student.tudelft.nl>2017-09-28 14:14:13 +0200
commit532aa9c9241de0b658499ea4bb04e1b3b7035082 (patch)
treeef8eeaa3ae65d25113ee45ee7747a1b89b17dc39
parent6eda14819b8c8a67b66eab9e04e82e141093f7da (diff)
Add notice about react-konva
-rw-r--r--README.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/README.md b/README.md
index f163e114..0b35877e 100644
--- a/README.md
+++ b/README.md
@@ -60,7 +60,9 @@ All pages are represented by a component in the `src/pages` directory. There are
### Components & Containers
-The building blocks of the UI are divided into so-called *components* and *containers* (as [encouraged](https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0) by the author of Redux). *Components* are considered 'pure', rendered as a function of input properties. *Containers*, on the other hand, are wrappers around *components*, injecting state through the properties of the components they wrap.
+The building blocks of the UI are divided into so-called *components* and *containers* ([as encouraged](https://medium.com/@dan_abramov/smart-and-dumb-components-7ca2f9a7c7d0) by the author of Redux). *Components* are considered 'pure', rendered as a function of input properties. *Containers*, on the other hand, are wrappers around *components*, injecting state through the properties of the components they wrap.
+
+Even the canvas (the main component of the app) is built using React components, with the help of the `react-konva` module. To illustrate: A rectangular object on the canvas is defined in a way that is not very different from how we define a standard `div` element on the splashpage.
### State Management
@@ -77,7 +79,7 @@ Files containing tests can be recognized by the `.test.js` suffix. They are usua
### Running all tests
-The following command runs all tests in the codebase. On top of this, it also watches the code for changes and reruns the tests when files are changed, automatically.
+The following command runs all tests in the codebase. On top of this, it also watches the code for changes and reruns the tests whenever any file is saved.
```bash
yarn test