1
- # ` Elm ` (_ ish_ ) ?
1
+ # ` Elm ` (_ ish_ )
2
+
3
+ ![ elmlogo-ish] ( https://user-images.githubusercontent.com/194400/43213139-b70a4c68-902d-11e8-8162-3c7cb56b6360.png )
4
+ <!-- the colors are deliberately "a bit off" to emphasize that
5
+ this is a "inspired by" but really a "poor immitation" of Elm! -->
2
6
3
7
` Elm ` (_ ish_ ) is our ** ` Elm ` ** -_ inspired_ ` JavaScript ` (** ES5** )
4
8
front-end _ micro_ -framework.[ <sup >1</sup >] ( #notes )
@@ -9,27 +13,27 @@ The purpose of building `Elm`(_ish_) is _not_ to "_replace_" Elm
9
13
or to create _ yet another_ front-end JS framework!
10
14
11
15
The purpose of _ separating_ the ` Elm ` (_ ish_ ) functions
12
- into a "micro framework" is: <br />
13
- ** a)** to *** simplify*** the Todo List application code. <br />
16
+ into a "micro framework" is to: <br />
17
+ ** a)** *** simplify*** the Todo List application code
18
+ to just "business logic". <br />
14
19
** b)** _ demonstrate_ a *** re-useable*** (_ fully-tested_ )
15
20
"** micro-framework** " that allows us to _ practice_ the Elm Architecture.<br />
16
- ** c)** get into the ** mindset** of writing ** tests _ first_ **
21
+ ** c)** promote the ** mindset** of writing ** tests _ first_ **
17
22
and ** ` then ` ** the _ least_ amount of code necessary to pass the test
18
23
(_ while meeting the acceptance criteria_ ).
19
24
20
25
By the end of this exercise you will _ understand_
21
26
The Elm Architecture (TEA) _ much better_
22
27
because we will be analysing, documenting, testing
23
28
and writing each function required
24
- to build the fully functional "micro framework" *** from scratch*** .
25
-
26
-
29
+ to build the _ fully functional_ "** micro framework** " *** from scratch*** .
27
30
28
31
29
32
## _ What?_
30
33
31
34
32
35
36
+
33
37
You are already _ familiar_ with the first few functions
34
38
` mount ` and ` empty `
35
39
0 commit comments