fix minor typos in todomvc example;

This commit is contained in:
Matthew Jaoudi 2017-07-25 15:19:25 -07:00
parent b9ccb58f60
commit f431eed2e7
3 changed files with 4 additions and 4 deletions

View File

@ -69,7 +69,7 @@
;; Use `reg-cofx` to register a "coeffect handler" which will inject the todos ;; Use `reg-cofx` to register a "coeffect handler" which will inject the todos
;; stored in localstore. ;; stored in localstore.
;; ;;
;; To see it used, look in `events.clj` at the event handler for `:initialise-db`. ;; To see it used, look in `events.cljs` at the event handler for `:initialise-db`.
;; That event handler has the interceptor `(inject-cofx :local-store-todos)` ;; That event handler has the interceptor `(inject-cofx :local-store-todos)`
;; The function registered below will be used to fulfill that request. ;; The function registered below will be used to fulfill that request.
;; ;;

View File

@ -35,7 +35,7 @@
;; When included in the interceptor chain of an event handler, this interceptor ;; When included in the interceptor chain of an event handler, this interceptor
;; runs `check-and-throw` `after` the event handler has finished, checking ;; runs `check-and-throw` `after` the event handler has finished, checking
;; the value for `app-db` against a spec. ;; the value for `app-db` against a spec.
;; If the event handler corrupted tha value for `app-db` an exception will be ;; If the event handler corrupted the value for `app-db` an exception will be
;; thrown. This helps us detect event handler bugs early. ;; thrown. This helps us detect event handler bugs early.
;; Because all state is held in `app-db`, we are effectively validating the ;; Because all state is held in `app-db`, we are effectively validating the
;; ENTIRE state of the application after each event handler runs. All of it. ;; ENTIRE state of the application after each event handler runs. All of it.

View File

@ -6,7 +6,7 @@
;; ;;
;; See https://github.com/Day8/re-frame/blob/master/docs/SubscriptionInfographic.md ;; See https://github.com/Day8/re-frame/blob/master/docs/SubscriptionInfographic.md
;; ;;
;; Layer 2 query functions, are "extractors". They take from `app-db` ;; Layer 2 query functions are "extractors". They take from `app-db`
;; and don't do any further computation on the extracted values. Any further ;; and don't do any further computation on the extracted values. Any further
;; computation should happen in Layer 3. ;; computation should happen in Layer 3.
;; Why? It is an efficiency thing. Every Layer 2 subscriptions will rerun anytime ;; Why? It is an efficiency thing. Every Layer 2 subscriptions will rerun anytime