mirror of
https://github.com/status-im/re-frame.git
synced 2025-02-22 14:58:12 +00:00
fix minor typos in todomvc example;
This commit is contained in:
parent
b9ccb58f60
commit
f431eed2e7
@ -52,7 +52,7 @@
|
||||
;;
|
||||
;; Part of the todomvc challenge is to store todos in LocalStorage, and
|
||||
;; on app startup, reload the todos from when the program was last run.
|
||||
;; But the challenge stipulates to NOT load the setting for the "showing"
|
||||
;; But the challenge stipulates to NOT load the setting for the "showing"
|
||||
;; filter. Just the todos.
|
||||
;;
|
||||
|
||||
@ -69,7 +69,7 @@
|
||||
;; Use `reg-cofx` to register a "coeffect handler" which will inject the todos
|
||||
;; 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)`
|
||||
;; The function registered below will be used to fulfill that request.
|
||||
;;
|
||||
|
@ -35,7 +35,7 @@
|
||||
;; When included in the interceptor chain of an event handler, this interceptor
|
||||
;; runs `check-and-throw` `after` the event handler has finished, checking
|
||||
;; 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.
|
||||
;; 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.
|
||||
|
@ -6,7 +6,7 @@
|
||||
;;
|
||||
;; 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
|
||||
;; computation should happen in Layer 3.
|
||||
;; Why? It is an efficiency thing. Every Layer 2 subscriptions will rerun anytime
|
||||
|
Loading…
x
Reference in New Issue
Block a user