|
3 | 3 | Learn how to build web applications using |
4 | 4 | the Elm ("Model Update View") Architecture in "_plain_" JavaScript. |
5 | 5 |
|
| 6 | +[](https://travis-ci.org/dwyl/learn-elm-architecture-in-javascript) |
6 | 7 | [](https://codecov.io/gh/dwyl/learn-elm-architecture-in-javascript) |
| 8 | +[](https://david-dm.org/dwyl/learn-elm-architecture-in-javascript) |
| 9 | +[](https://david-dm.org/dwyl/learn-elm-architecture-in-javascript?type=dev) |
7 | 10 |
|
8 | 11 |
|
9 | 12 | > We think Elm is the _future_ of Front End Web Development <br /> |
@@ -56,7 +59,7 @@ When compared to _other_ ways of organizing your code, |
56 | 59 | "MUV" has the following benefits: |
57 | 60 | + Easier to _understand_ what is going on in more advanced apps |
58 | 61 | because the "_flow_" is always the same. |
59 | | -+ ***Uni-directional data-flow*** means "state" is always predictable: |
| 62 | ++ ***Uni-directional data-flow*** means "state" of the app is always predictable; |
60 | 63 | given a specific starting "state" and sequence of update actions |
61 | 64 | the output/end state will _always_ be the same. This makes testing/testability |
62 | 65 | very easy! |
|
0 commit comments