["^ ","~:output",["^ ","~:js","goog.provide('re_frame.core');\n/**\n * Queue `event` for processing (handling). \n * \n *   `event` is a vector and the first element is typically a keyword\n *   which identifies the kind of event.\n * \n *   The event will be added to a FIFO processing queue, so event\n *   handling does not happen immediately. It will happen 'very soon'\n *   bit not now. And if the queue already contains events, they\n *   will be processed first.\n * \n *   Usage:\n *    \n *    (dispatch [:order \"pizza\" {:supreme 2 :meatlovers 1 :veg 1}])\n *   \n */\nre_frame.core.dispatch = (function re_frame$core$dispatch(event){\nreturn re_frame.router.dispatch(event);\n});\n/**\n * Synchronously (immediately) process `event`. It does **not** queue\n *   the event for handling later as `dispatch` does. \n *   \n *   `event` is a vector and the first element is typically a keyword \n *   which identifies the kind of event.\n * \n *   It is an error to use `dispatch-sync` within an event handler because \n *   you can't immediately process an new event when one is already\n *   part way through being processed.\n * \n *   Generally, avoid using this function, and instead, use `dispatch`. \n *   Only use it in the narrow set of cases where any delay in \n *   processing is a problem:\n * \n *  1. the `:on-change` handler of a text field where we are expecting fast typing\n *  2. when initialising your app - see 'main' in examples/todomvc/src/core.cljs\n *  3. in a unit test where immediate, synchronous processing is useful\n * \n *   Usage:\n * \n *    (dispatch-sync [:sing :falsetto \"piano accordion\"])\n *   \n */\nre_frame.core.dispatch_sync = (function re_frame$core$dispatch_sync(event){\nreturn re_frame.router.dispatch_sync(event);\n});\n/**\n * A call to `reg-sub` associates a `query-id` WITH two functions.\n * \n *   The two functions provide 'a mechanism' for creating a node \n *   in the Signal Graph. When a node of type `query-id` is needed, \n *   the two functions can be used to create it.\n *   \n *   The three arguments are: \n * \n *   - `query-id` - typically a namespaced keyword (later used in subscribe)\n *   - optionally, an `input signals` function which returns the input data\n *  flows required by this kind of node. \n *   - a `computation function` which computes the value (output) of the \n *  node (from the input data flows)\n *   \n *   Later, during app execution, a call to `(subscribe [:sub-id 3 :blue])`,\n *   will trigger the need for a new `:sub-id` Signal Graph node (matching the \n *   query `[:sub-id 3 :blue]`). And, to create that node the two functions \n *   associated with `:sub-id` will be looked up and used.\n * \n *   Just to be clear: calling `reg-sub` does not immediately create a node. \n *   It only registers 'a mechanism' (the two functions) by which nodes \n *   can be created later, when a node is bought into existence by the \n *   use of `subscribe` in a `View Function`.\n * \n *   The `computation function` is expected to take two arguments:\n *   \n *  - `input-values` - the values which flow into this node (how is it wierd into the graph?)\n *  - `query-vector` - the vector given to `subscribe`\n *   \n *   and it returns a computed value (which then becomes the output of the node)\n * \n *   When `computation function` is called, the 2nd `query-vector` argument will be that \n *   vector supplied to the `subscribe`. So, if the call was `(subscribe [:sub-id 3 :blue])`,\n *   then the `query-vector` supplied to the computaton function will be `[:sub-id 3 :blue]`.\n * \n *   The argument(s) supplied to `reg-sub` between `query-id` and the `computation-function` \n *   can vary in 3 ways, but whatever is there defines the `input signals` part \n *   of `the mechanism`, specifying what input values \"flow into\" the \n *   `computation function` (as the 1st argument) when it is called.\n * \n *   So, `reg-sub` can be called in one of three ways, because there are three ways \n *   to define the input signals part. But note, the 2nd method, in which a \n *   `signals function` is explicitly supplied, is the most canonical and \n *   instructive. The other two are really just sugary variations.\n * \n *   **First variation** - no input signal function given:\n * \n *    (reg-sub\n *      :query-id\n *      a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n * \n *   In the absence of an explicit `signals function`, the node's input signal defaults to `app-db`\n *   and, as a result, the value within `app-db` (a map) is\n *   is given as the 1st argument when `a-computation-fn` is called.\n * \n * \n *   **Second variation** - a signal function is explicitly supplied:\n * \n *    (reg-sub\n *      :query-id\n *      signal-fn     ;; <-- here\n *      computation-fn)\n * \n *   This is the most canonical and instructive of the three variations.\n * \n *   When a node is created from the template, the `signal function` will be called and it\n *   is expected to return the input signal(s) as either a singleton, if there is only\n *   one, or a sequence if there are many, or a map with the signals as the values.\n * \n *   The current values of the returned signals will be supplied as the 1st argument to\n *   the `a-computation-fn` when it is called - and subject to what this `signal-fn` returns,\n *   this value will be either a singleton, sequence or map of them (paralleling\n *   the structure returned by the `signal function`).\n * \n *   This example `signal function` returns a 2-vector of input signals.\n * \n *    (fn [query-vec dynamic-vec]\n *       [(subscribe [:a-sub])\n *        (subscribe [:b-sub])])\n * \n *   The associated computation function must be written\n *   to expect a 2-vector of values for its first argument:\n * \n *    (fn [[a b] query-vec]     ;; 1st argument is a seq of two values\n *      ....)\n * \n *   If, on the other hand, the signal function was simpler and returned a singleton, like this:\n * \n *   (fn [query-vec dynamic-vec]\n *     (subscribe [:a-sub]))      ;; <-- returning a singleton\n * \n *   then the associated computation function must be written to expect a single value\n *   as the 1st argument:\n * \n *    (fn [a query-vec]       ;; 1st argument is a single value\n *       ...)\n * \n *   Further Note: variation #1 above, in which an `input-fn` was not supplied, like this:\n * \n *    (reg-sub\n *      :query-id\n *      a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n * \n *   is the equivalent of using this\n *   2nd variation and explicitly suppling a `signal-fn` which returns `app-db`:\n * \n *    (reg-sub\n *      :query-id\n *      (fn [_ _]  re-frame/app-db)   ;; <--- explicit signal-fn\n *      a-computation-fn)             ;; has signature:  (fn [db query-vec]  ... ret-value)\n * \n *   **Third variation** - syntax Sugar\n * \n *    (reg-sub\n *      :a-b-sub\n *      :<- [:a-sub]\n *      :<- [:b-sub]\n *      (fn [[a b] query-vec]    ;; 1st argument is a seq of two values\n *        {:a a :b b}))\n * \n *   This 3rd variation is just syntactic sugar for the 2nd.  Instead of providing an\n *   `signals-fn` you provide one or more pairs of `:<-` and a subscription vector.\n * \n *   If you supply only one pair a singleton will be supplied to the computation function,\n *   as if you had supplied a `signal-fn` returning only a single value:\n * \n * \n *    (reg-sub\n *      :a-sub\n *      :<- [:a-sub]\n *      (fn [a query-vec]      ;; only one pair, so 1st argument is a single value\n *        ...))\n * \n *   For further understanding, read the tutorials, and look at the detailed comments in\n *   /examples/todomvc/src/subs.cljs.\n *      \n *   See also: `subscribe`\n *   \n */\nre_frame.core.reg_sub = (function re_frame$core$reg_sub(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49439 = arguments.length;\nvar i__4737__auto___49440 = (0);\nwhile(true){\nif((i__4737__auto___49440 < len__4736__auto___49439)){\nargs__4742__auto__.push((arguments[i__4737__auto___49440]));\n\nvar G__49441 = (i__4737__auto___49440 + (1));\ni__4737__auto___49440 = G__49441;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((1) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((1)),(0),null)):null);\nreturn re_frame.core.reg_sub.cljs$core$IFn$_invoke$arity$variadic((arguments[(0)]),argseq__4743__auto__);\n});\n\n(re_frame.core.reg_sub.cljs$core$IFn$_invoke$arity$variadic = (function (query_id,args){\nreturn cljs.core.apply.cljs$core$IFn$_invoke$arity$2(re_frame.subs.reg_sub,cljs.core.into.cljs$core$IFn$_invoke$arity$2(new cljs.core.PersistentVector(null, 1, 5, cljs.core.PersistentVector.EMPTY_NODE, [query_id], null),args));\n}));\n\n(re_frame.core.reg_sub.cljs$lang$maxFixedArity = (1));\n\n/** @this {Function} */\n(re_frame.core.reg_sub.cljs$lang$applyTo = (function (seq49163){\nvar G__49164 = cljs.core.first(seq49163);\nvar seq49163__$1 = cljs.core.next(seq49163);\nvar self__4723__auto__ = this;\nreturn self__4723__auto__.cljs$core$IFn$_invoke$arity$variadic(G__49164,seq49163__$1);\n}));\n\n/**\n * Given a `query` vector, returns a Reagent `reaction` which will, over\n *   time, reactively deliver a stream of values. So, in FRP-ish terms,\n *   it returns a `Signal`.\n * \n *   To obtain the current value from the Signal, it must be dereferenced: \n *   \n *    (let [signal (subscribe [:items])\n *          value  (deref signal)]     ;; could be written as @signal\n *      ...)\n * \n * which is typically written tersely as simple:\n * \n *    (let [items  @(subscribe [:items])] \n *      ...)\n *    \n * \n *   `query` is a vector of at least one element. The first element is the\n *   `query-id`, typically a namespaced keyword. The rest of the vector's\n *   elements are optional, additional values which parameterise the query\n *   performed.\n * \n *   `dynv` is an optional 3rd argument, which is a vector of further input\n *   signals (atoms, reactions, etc), NOT values. This argument exists for\n *   historical reasons and is borderline deprecated these days.\n * \n *   **Example Usage**:\n * \n *    (subscribe [:items])\n *    (subscribe [:items \"blue\" :small])\n *    (subscribe [:items {:colour \"blue\"  :size :small}])\n *  \n *   Note: for any given call to `subscribe` there must have been a previous call\n *   to `reg-sub`, registering the query handler (functions) associated with \n *   `query-id`.\n * \n *   **Hint**\n * \n *   When used in a view function BE SURE to `deref` the returned value.\n *   In fact, to avoid any mistakes, some prefer to define:\n *   \n *    (def <sub  (comp deref re-frame.core/subscribe))\n *  \n *   And then, within their views, they call  `(<sub [:items :small])` rather\n *   than using `subscribe` directly.\n * \n *   **De-duplication**\n * \n *   Two, or more, concurrent subscriptions for the same query will \n *   source reactive updates from the one executing handler.\n *    \n *   See also: `reg-sub`\n *   \n */\nre_frame.core.subscribe = (function re_frame$core$subscribe(var_args){\nvar G__49179 = arguments.length;\nswitch (G__49179) {\ncase 1:\nreturn re_frame.core.subscribe.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ncase 2:\nreturn re_frame.core.subscribe.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.subscribe.cljs$core$IFn$_invoke$arity$1 = (function (query){\nreturn re_frame.subs.subscribe.cljs$core$IFn$_invoke$arity$1(query);\n}));\n\n(re_frame.core.subscribe.cljs$core$IFn$_invoke$arity$2 = (function (query,dynv){\nreturn re_frame.subs.subscribe.cljs$core$IFn$_invoke$arity$2(query,dynv);\n}));\n\n(re_frame.core.subscribe.cljs$lang$maxFixedArity = 2);\n\n/**\n * Unregisters subscription handlers (presumably registered previously via the use of `reg-sub`). \n * \n *   When called with no args, it will unregister all currently registered subscription handlers. \n * \n *   When given one arg, assumed to be the `id` of a previously registered \n *   subscription handler, it will unregister the associated handler. Will produce a warning to \n *   console if it finds no matching registration.\n * \n *   NOTE: Depending on the usecase, it may be necessary to call `clear-subscription-cache!` afterwards\n */\nre_frame.core.clear_sub = (function re_frame$core$clear_sub(var_args){\nvar G__49195 = arguments.length;\nswitch (G__49195) {\ncase 0:\nreturn re_frame.core.clear_sub.cljs$core$IFn$_invoke$arity$0();\n\nbreak;\ncase 1:\nreturn re_frame.core.clear_sub.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.clear_sub.cljs$core$IFn$_invoke$arity$0 = (function (){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$1(re_frame.subs.kind);\n}));\n\n(re_frame.core.clear_sub.cljs$core$IFn$_invoke$arity$1 = (function (query_id){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$2(re_frame.subs.kind,query_id);\n}));\n\n(re_frame.core.clear_sub.cljs$lang$maxFixedArity = 1);\n\n/**\n * Removes all subscriptions from the cache.\n * \n *   This function can be used at development time or test time. Useful when hot realoding\n *   namespaces containing subscription handlers. Also call it after a React/render exception,\n *   because React components won't have been cleaned up properly. And this, in turn, means \n *   the subscriptions within those components won't have been cleaned up correctly. So this \n *   forces the issue.\n *   \n */\nre_frame.core.clear_subscription_cache_BANG_ = (function re_frame$core$clear_subscription_cache_BANG_(){\nreturn re_frame.subs.clear_subscription_cache_BANG_();\n});\n/**\n * This is a low level, advanced function.  You should probably be\n *   using `reg-sub` instead.\n * \n *   Some explanation is available in the docs at\n *   <a href=\"http://day8.github.io/re-frame/flow-mechanics/\" target=\"_blank\">http://day8.github.io/re-frame/flow-mechanics/</a>\n */\nre_frame.core.reg_sub_raw = (function re_frame$core$reg_sub_raw(query_id,handler_fn){\nreturn re_frame.registrar.register_handler(re_frame.subs.kind,query_id,handler_fn);\n});\n/**\n * Register the given effect `handler` for the given `id`:\n * \n *  - `id` is keyword, often namespaced.\n *  - `handler` is a side-effecting function which takes a single argument and whose return\n *    value is ignored.\n * \n *   To use, first, associate `:effect2` with a handler:\n * \n *    (reg-fx\n *       :effect2\n *       (fn [value]\n *          ... do something side-effect-y))\n * \n *   Then, later, if an event handler were to return this effects map:\n * \n *    {:effect2  [1 2]}\n * \n *   then the `handler` `fn` we registered previously, using `reg-fx`, will be\n *   called with an argument of `[1 2]`.\n *   \n */\nre_frame.core.reg_fx = (function re_frame$core$reg_fx(id,handler){\nreturn re_frame.fx.reg_fx(id,handler);\n});\n/**\n * Unregisters effect handlers (presumably registered previously via the use of `reg-fx`). \n * \n *   When called with no args, it will unregister all currently registered effect handlers. \n * \n *   When given one arg, assumed to be the `id` of a previously registered \n *   effect handler, it will unregister the associated handler. Will produce a warning to \n *   console if it finds no matching registration.\n *   \n */\nre_frame.core.clear_fx = (function re_frame$core$clear_fx(var_args){\nvar G__49219 = arguments.length;\nswitch (G__49219) {\ncase 0:\nreturn re_frame.core.clear_fx.cljs$core$IFn$_invoke$arity$0();\n\nbreak;\ncase 1:\nreturn re_frame.core.clear_fx.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.clear_fx.cljs$core$IFn$_invoke$arity$0 = (function (){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$1(re_frame.fx.kind);\n}));\n\n(re_frame.core.clear_fx.cljs$core$IFn$_invoke$arity$1 = (function (id){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$2(re_frame.fx.kind,id);\n}));\n\n(re_frame.core.clear_fx.cljs$lang$maxFixedArity = 1);\n\n/**\n * Register the given coeffect `handler` for the given `id`, for later use\n *   within `inject-cofx`:\n * \n *  - `id` is keyword, often namespaced.\n *  - `handler` is a function which takes either one or two arguements, the first of which is\n *     always `coeffects` and which returns an updated `coeffects`.\n * \n *   See also: `inject-cofx` \n *   \n */\nre_frame.core.reg_cofx = (function re_frame$core$reg_cofx(id,handler){\nreturn re_frame.cofx.reg_cofx(id,handler);\n});\n/**\n * Given an `id`, and an optional, arbitrary `value`, returns an interceptor\n *   whose `:before` adds to the `:coeffects` (map) by calling a pre-registered\n *   'coeffect handler' identified by the `id`.\n * \n *   The previous association of a `coeffect handler` with an `id` will have\n *   happened via a call to `re-frame.core/reg-cofx` - generally on program startup.\n * \n *   Within the created interceptor, this 'looked up' `coeffect handler` will\n *   be called (within the `:before`) with two arguments:\n * \n *   - the current value of `:coeffects`\n *   - optionally, the originally supplied arbitrary `value`\n * \n *   This `coeffect handler` is expected to modify and return its first, `coeffects` argument.\n * \n *   **Example of `inject-cofx` and `reg-cofx` working together**\n * \n * \n *   First - Early in app startup, you register a `coeffect handler` for `:datetime`:\n * \n *    (re-frame.core/reg-cofx\n *      :datetime                        ;; usage  (inject-cofx :datetime)\n *      (fn coeffect-handler\n *        [coeffect]\n *        (assoc coeffect :now (js/Date.))))   ;; modify and return first arg\n * \n *   Second - Later, add an interceptor to an -fx event handler, using `inject-cofx`:\n * \n *    (re-frame.core/reg-event-fx            ;; when registering an event handler\n *      :event-id\n *      [ ... (inject-cofx :datetime) ... ]  ;; <-- create an injecting interceptor\n *      (fn event-handler\n *        [coeffect event]\n *          ;;... in here can access (:now coeffect) to obtain current datetime ... \n *        )))\n * \n *   **Background**\n * \n *   `coeffects` are the input resources required by an event handler\n *   to perform its job. The two most obvious ones are `db` and `event`.\n *   But sometimes an event handler might need other resources.\n * \n *   Perhaps an event handler needs a random number or a GUID or the current\n *   datetime. Perhaps it needs access to a DataScript database connection.\n * \n *   If an event handler directly accesses these resources, it stops being\n *   pure and, consequently, it becomes harder to test, etc. So we don't\n *   want that.\n * \n *   Instead, the interceptor created by this function is a way to 'inject'\n *   'necessary resources' into the `:coeffects` (map) subsequently given\n *   to the event handler at call time.\n *        \n *   See also `reg-cofx`\n *   \n */\nre_frame.core.inject_cofx = (function re_frame$core$inject_cofx(var_args){\nvar G__49237 = arguments.length;\nswitch (G__49237) {\ncase 1:\nreturn re_frame.core.inject_cofx.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ncase 2:\nreturn re_frame.core.inject_cofx.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.inject_cofx.cljs$core$IFn$_invoke$arity$1 = (function (id){\nreturn re_frame.cofx.inject_cofx.cljs$core$IFn$_invoke$arity$1(id);\n}));\n\n(re_frame.core.inject_cofx.cljs$core$IFn$_invoke$arity$2 = (function (id,value){\nreturn re_frame.cofx.inject_cofx.cljs$core$IFn$_invoke$arity$2(id,value);\n}));\n\n(re_frame.core.inject_cofx.cljs$lang$maxFixedArity = 2);\n\n/**\n * Unregisters coeffect handlers (presumably registered previously via the use of `reg-cofx`). \n * \n *   When called with no args, it will unregister all currently registered coeffect handlers. \n * \n *   When given one arg, assumed to be the `id` of a previously registered \n *   coeffect handler, it will unregister the associated handler. Will produce a warning to \n *   console if it finds no matching registration.\n */\nre_frame.core.clear_cofx = (function re_frame$core$clear_cofx(var_args){\nvar G__49249 = arguments.length;\nswitch (G__49249) {\ncase 0:\nreturn re_frame.core.clear_cofx.cljs$core$IFn$_invoke$arity$0();\n\nbreak;\ncase 1:\nreturn re_frame.core.clear_cofx.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.clear_cofx.cljs$core$IFn$_invoke$arity$0 = (function (){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$1(re_frame.cofx.kind);\n}));\n\n(re_frame.core.clear_cofx.cljs$core$IFn$_invoke$arity$1 = (function (id){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$2(re_frame.cofx.kind,id);\n}));\n\n(re_frame.core.clear_cofx.cljs$lang$maxFixedArity = 1);\n\n/**\n * Register the given event `handler` (function) for the given `id`. Optionally, provide\n *   an `interceptors` chain:\n * \n *  - `id` is typically a namespaced keyword  (but can be anything)\n *  - `handler` is a function: (db event) -> db\n *  - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n * \n *   Example Usage:\n * \n *    (reg-event-db \n *      :token \n *      (fn [db event]\n *        (assoc db :some-key (get event 2)))  ;; return updated db\n * \n *   Or perhaps:\n * \n *    (reg-event-db\n *      :namespaced/id           ;; <-- namespaced keywords are often used\n *      [one two three]          ;; <-- a seq of interceptors\n *      (fn [db [_ arg1 arg2]]   ;; <-- event vector is destructured\n *        (-> db \n *          (dissoc arg1)\n *          (update :key + arg2))))   ;; return updated db\n *   \n */\nre_frame.core.reg_event_db = (function re_frame$core$reg_event_db(var_args){\nvar G__49272 = arguments.length;\nswitch (G__49272) {\ncase 2:\nreturn re_frame.core.reg_event_db.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ncase 3:\nreturn re_frame.core.reg_event_db.cljs$core$IFn$_invoke$arity$3((arguments[(0)]),(arguments[(1)]),(arguments[(2)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.reg_event_db.cljs$core$IFn$_invoke$arity$2 = (function (id,handler){\nreturn re_frame.core.reg_event_db.cljs$core$IFn$_invoke$arity$3(id,null,handler);\n}));\n\n(re_frame.core.reg_event_db.cljs$core$IFn$_invoke$arity$3 = (function (id,interceptors,handler){\nreturn re_frame.events.register(id,new cljs.core.PersistentVector(null, 5, 5, cljs.core.PersistentVector.EMPTY_NODE, [re_frame.cofx.inject_db,re_frame.fx.do_fx,re_frame.std_interceptors.inject_global_interceptors,interceptors,re_frame.std_interceptors.db_handler__GT_interceptor(handler)], null));\n}));\n\n(re_frame.core.reg_event_db.cljs$lang$maxFixedArity = 3);\n\n/**\n * Register the given event `handler` (function) for the given `id`. Optionally, provide\n *   an `interceptors` chain:\n * \n *  - `id` is typically a namespaced keyword  (but can be anything)\n *  - `handler` is a function: (coeffects-map event-vector) -> effects-map\n *  - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n * \n * \n *   Example Usage:\n * \n *    (reg-event-fx \n *      :token \n *      (fn [cofx event]\n *        {:db (assoc (:db cofx) :some-key (get event 2))}))   ;; return a map of effects\n * \n * \n *   Or perhaps:\n * \n *    (reg-event-fx\n *      :namespaced/id           ;; <-- namespaced keywords are often used\n *      [one two three]          ;; <-- a seq of interceptors\n *      (fn [{:keys [db] :as cofx} [_ arg1 arg2]] ;; destructure both arguments\n *        {:db       (assoc db :some-key arg1)          ;; return a map of effects\n *         :dispatch [:some-event arg2]}))\n *   \n */\nre_frame.core.reg_event_fx = (function re_frame$core$reg_event_fx(var_args){\nvar G__49285 = arguments.length;\nswitch (G__49285) {\ncase 2:\nreturn re_frame.core.reg_event_fx.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ncase 3:\nreturn re_frame.core.reg_event_fx.cljs$core$IFn$_invoke$arity$3((arguments[(0)]),(arguments[(1)]),(arguments[(2)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.reg_event_fx.cljs$core$IFn$_invoke$arity$2 = (function (id,handler){\nreturn re_frame.core.reg_event_fx.cljs$core$IFn$_invoke$arity$3(id,null,handler);\n}));\n\n(re_frame.core.reg_event_fx.cljs$core$IFn$_invoke$arity$3 = (function (id,interceptors,handler){\nreturn re_frame.events.register(id,new cljs.core.PersistentVector(null, 5, 5, cljs.core.PersistentVector.EMPTY_NODE, [re_frame.cofx.inject_db,re_frame.fx.do_fx,re_frame.std_interceptors.inject_global_interceptors,interceptors,re_frame.std_interceptors.fx_handler__GT_interceptor(handler)], null));\n}));\n\n(re_frame.core.reg_event_fx.cljs$lang$maxFixedArity = 3);\n\n/**\n * Register the given event `handler` (function) for the given `id`. Optionally, provide\n *   an `interceptors` chain:\n * \n *  - `id` is typically a namespaced keyword  (but can be anything)\n *  - `handler` is a function: (context-map event-vector) -> context-map\n * \n *   This form of registration is seldomAt dinner wenever used.\n *   \n */\nre_frame.core.reg_event_ctx = (function re_frame$core$reg_event_ctx(var_args){\nvar G__49288 = arguments.length;\nswitch (G__49288) {\ncase 2:\nreturn re_frame.core.reg_event_ctx.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ncase 3:\nreturn re_frame.core.reg_event_ctx.cljs$core$IFn$_invoke$arity$3((arguments[(0)]),(arguments[(1)]),(arguments[(2)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.reg_event_ctx.cljs$core$IFn$_invoke$arity$2 = (function (id,handler){\nreturn re_frame.core.reg_event_ctx.cljs$core$IFn$_invoke$arity$3(id,null,handler);\n}));\n\n(re_frame.core.reg_event_ctx.cljs$core$IFn$_invoke$arity$3 = (function (id,interceptors,handler){\nreturn re_frame.events.register(id,new cljs.core.PersistentVector(null, 5, 5, cljs.core.PersistentVector.EMPTY_NODE, [re_frame.cofx.inject_db,re_frame.fx.do_fx,re_frame.std_interceptors.inject_global_interceptors,interceptors,re_frame.std_interceptors.ctx_handler__GT_interceptor(handler)], null));\n}));\n\n(re_frame.core.reg_event_ctx.cljs$lang$maxFixedArity = 3);\n\n/**\n * Unregisters event handlers (presumably registered previously via the use of `reg-event-db` or `reg-event-fx`). \n * \n *   When called with no args, it will unregister all currently registered event handlers. \n * \n *   When given one arg, assumed to be the `id` of a previously registered \n *   event handler, it will unregister the associated handler. Will produce a warning to \n *   console if it finds no matching registration.\n */\nre_frame.core.clear_event = (function re_frame$core$clear_event(var_args){\nvar G__49294 = arguments.length;\nswitch (G__49294) {\ncase 0:\nreturn re_frame.core.clear_event.cljs$core$IFn$_invoke$arity$0();\n\nbreak;\ncase 1:\nreturn re_frame.core.clear_event.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.clear_event.cljs$core$IFn$_invoke$arity$0 = (function (){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$1(re_frame.events.kind);\n}));\n\n(re_frame.core.clear_event.cljs$core$IFn$_invoke$arity$1 = (function (id){\nreturn re_frame.registrar.clear_handlers.cljs$core$IFn$_invoke$arity$2(re_frame.events.kind,id);\n}));\n\n(re_frame.core.clear_event.cljs$lang$maxFixedArity = 1);\n\n/**\n * An interceptor which logs/instruments an event handler's actions to\n *   `js/console.debug`. See examples/todomvc/src/events.cljs for use.\n * \n *   Output includes:\n * \n *  1. the event vector\n *  2. a `clojure.data/diff` of db, before vs after, which shows\n *     the changes caused by the event handler. To understand the output,\n *     you should understand:\n *     <a href=\"https://clojuredocs.org/clojure.data/diff\" target=\"_blank\">https://clojuredocs.org/clojure.data/diff</a>.\n * \n *   You'd typically include this interceptor after (to the right of) any\n *   `path` interceptor.\n * \n *   Warning:  calling `clojure.data/diff` on large, complex data structures\n *   can be slow. So, you won't want this interceptor present in production\n *   code. So, you should condition it out like this:\n * \n *    (re-frame.core/reg-event-db\n *      :evt-id\n *      [(when ^boolean goog.DEBUG re-frame.core/debug)]  ;; <-- conditional\n *      (fn [db v]\n *         ...))\n * \n *   To make this code fragment work, you'll also have to set `goog.DEBUG` to\n *   `false` in your production builds. For an example, look in `project.clj` of /examples/todomvc.\n *   \n */\nre_frame.core.debug = re_frame.std_interceptors.debug;\n/**\n * Returns an interceptor which acts somewhat like `clojure.core/update-in`, in the sense that \n *   the event handler is given a specific part of `app-db` to change, not all of `app-db`. \n * \n *   The interceptor has both a `:before` and `:after` functions. The `:before` replaces  \n *   the `:db` key within coeffects with a sub-path within `app-db`. The `:after` reverses the process, \n *   and it grafts the handler's return value back into db, at the right path.\n * \n *   Examples:\n * \n *    (path :some :path)\n *    (path [:some :path])\n *    (path [:some :path] :to :here)\n *    (path [:some :path] [:to] :here)\n * \n *   Example Use:\n * \n *    (reg-event-db\n *      :event-id\n *      (path [:a :b])  ;; <-- used here, in interceptor chain\n *      (fn [b v]       ;; 1st arg is not db. Is the value from path [:a :b] within db\n *        ... new-b))   ;; returns a new value for that path (not the entire db)\n * \n *   Notes:\n *   \n *  1. `path` may appear more than once in an interceptor chain. Progressive narrowing.\n *  2. if `:effects` contains no `:db` effect, can't graft a value back in.\n *   \n */\nre_frame.core.path = (function re_frame$core$path(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49473 = arguments.length;\nvar i__4737__auto___49474 = (0);\nwhile(true){\nif((i__4737__auto___49474 < len__4736__auto___49473)){\nargs__4742__auto__.push((arguments[i__4737__auto___49474]));\n\nvar G__49475 = (i__4737__auto___49474 + (1));\ni__4737__auto___49474 = G__49475;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((0) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((0)),(0),null)):null);\nreturn re_frame.core.path.cljs$core$IFn$_invoke$arity$variadic(argseq__4743__auto__);\n});\n\n(re_frame.core.path.cljs$core$IFn$_invoke$arity$variadic = (function (args){\nreturn cljs.core.apply.cljs$core$IFn$_invoke$arity$2(re_frame.std_interceptors.path,args);\n}));\n\n(re_frame.core.path.cljs$lang$maxFixedArity = (0));\n\n/** @this {Function} */\n(re_frame.core.path.cljs$lang$applyTo = (function (seq49298){\nvar self__4724__auto__ = this;\nreturn self__4724__auto__.cljs$core$IFn$_invoke$arity$variadic(cljs.core.seq(seq49298));\n}));\n\n/**\n * Returns an Interceptor which will run the given function `f` in the `:after`\n *   position.  \n * \n *   `f` is called with two arguments: `db` and `v`, and is expected to\n *   return a modified `db`.\n * \n *   Unlike the `after` interceptor which is only about side effects, `enrich`\n *   expects `f` to process and alter the given `db` coeffect in some useful way,\n *   contributing to the derived data, flowing vibe.\n * \n *   #### Example Use:\n * \n *   Imagine that todomvc needed to do duplicate detection - if any two todos had\n *   the same text, then highlight their background, and report them via a warning\n *   at the bottom of the panel.\n * \n *   Almost any user action (edit text, add new todo, remove a todo) requires a\n *   complete reassessment of duplication errors and warnings. Eg: that edit\n *   just made might have introduced a new duplicate, or removed one. Same with\n *   any todo removal. So we need to re-calculate warnings after any CRUD events\n *   associated with the todos list.\n * \n *   Unless we are careful, we might end up coding subtly different checks\n *   for each kind of CRUD operation.  The duplicates check made after\n *   'delete todo' event might be subtly different to that done after an\n *   editing operation. Nice and efficient, but fiddly. A bug generator\n *   approach.\n * \n *   So, instead, we create an `f` which recalculates ALL warnings from scratch\n *   every time there is ANY change. It will inspect all the todos, and\n *   reset ALL FLAGS every time (overwriting what was there previously)\n *   and fully recalculate the list of duplicates (displayed at the bottom?).\n * \n *   <a href=\"https://twitter.com/nathanmarz/status/879722740776939520\" target=\"_blank\">https://twitter.com/nathanmarz/status/879722740776939520</a>\n * \n *   By applying `f` in an `:enrich` interceptor, after every CRUD event,\n *   we keep the handlers simple and yet we ensure this important step\n *   (of getting warnings right) is not missed on any change.\n * \n *   We can test `f` easily - it is a pure function - independently of\n *   any CRUD operation.\n * \n *   This brings huge simplicity at the expense of some re-computation\n *   each time. This may be a very satisfactory trade-off in many cases.\n */\nre_frame.core.enrich = (function re_frame$core$enrich(f){\nreturn re_frame.std_interceptors.enrich(f);\n});\n/**\n * An interceptor which removes the first element of the event vector,\n *   before it is supplied to the event handler, allowing you to write more\n * aesthetically pleasing event handlers. No leading underscore on the event-v!\n * \n *   Your event handlers will look like this:\n * \n *    (reg-event-db\n *      :event-id\n *      [... trim-v ...]    ;; <-- added to the interceptors\n *      (fn [db [x y z]]    ;; <-- instead of [_ x y z]\n *        ...)\n *  \n */\nre_frame.core.trim_v = re_frame.std_interceptors.trim_v;\n/**\n * Returns an interceptor which runs the given function `f` in the `:after`\n *   position, presumably for side effects.\n * \n *   `f` is called with two arguments: the `:effects` value for `:db`\n *   (or the `:coeffect` value of `:db` if no `:db` effect is returned) and the event.\n *   Its return value is ignored, so `f` can only side-effect.\n * \n *   An example of use can be seen in the re-frame github repo in `/examples/todomvc/events.cljs`:\n * \n *   - `f` runs schema validation (reporting any errors found).\n *   - `f` writes to localstorage.\n */\nre_frame.core.after = (function re_frame$core$after(f){\nreturn re_frame.std_interceptors.after(f);\n});\n/**\n * Returns an interceptor which will observe N paths within `db`, and if any of them\n *   test not identical? to their previous value  (as a result of a event handler\n *   being run), then it will run `f` to compute a new value, which is then assoc-ed\n *   into the given `out-path` within `db`.\n * \n *   Example Usage:\n * \n *    (defn my-f\n *      [a-val b-val]\n *      ... some computation on a and b in here)\n * \n *    ;; use it\n *    (def my-interceptor (on-changes my-f [:c] [:a] [:b]))\n * \n *    (reg-event-db\n *      :event-id\n *      [... my-interceptor ...]  ;; <-- ultimately used here\n *      (fn [db v]\n *         ...))\n * \n * \n *   If you put this Interceptor on handlers which might change paths `:a` or `:b`,\n *   it will:\n * \n *  - call `f` each time the value at path `[:a]` or `[:b]` changes\n *  - call `f` with the values extracted from `[:a]` `[:b]`\n *  - assoc the return value from `f` into the path  `[:c]`\n *   \n */\nre_frame.core.on_changes = (function re_frame$core$on_changes(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49478 = arguments.length;\nvar i__4737__auto___49479 = (0);\nwhile(true){\nif((i__4737__auto___49479 < len__4736__auto___49478)){\nargs__4742__auto__.push((arguments[i__4737__auto___49479]));\n\nvar G__49480 = (i__4737__auto___49479 + (1));\ni__4737__auto___49479 = G__49480;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((2) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((2)),(0),null)):null);\nreturn re_frame.core.on_changes.cljs$core$IFn$_invoke$arity$variadic((arguments[(0)]),(arguments[(1)]),argseq__4743__auto__);\n});\n\n(re_frame.core.on_changes.cljs$core$IFn$_invoke$arity$variadic = (function (f,out_path,in_paths){\nreturn cljs.core.apply.cljs$core$IFn$_invoke$arity$2(re_frame.std_interceptors.on_changes,cljs.core.into.cljs$core$IFn$_invoke$arity$2(new cljs.core.PersistentVector(null, 2, 5, cljs.core.PersistentVector.EMPTY_NODE, [f,out_path], null),in_paths));\n}));\n\n(re_frame.core.on_changes.cljs$lang$maxFixedArity = (2));\n\n/** @this {Function} */\n(re_frame.core.on_changes.cljs$lang$applyTo = (function (seq49315){\nvar G__49316 = cljs.core.first(seq49315);\nvar seq49315__$1 = cljs.core.next(seq49315);\nvar G__49317 = cljs.core.first(seq49315__$1);\nvar seq49315__$2 = cljs.core.next(seq49315__$1);\nvar self__4723__auto__ = this;\nreturn self__4723__auto__.cljs$core$IFn$_invoke$arity$variadic(G__49316,G__49317,seq49315__$2);\n}));\n\n/**\n * Registers the given `interceptor` as a global interceptor. Global interceptors are\n * included in the processing chain of every event.\n * \n * When you register an event handler, you have the option of supplying an\n * interceptor chain. Any global interceptors you register are effectively\n * prepending to this chain.\n * \n * Global interceptors are run in the order that they are registered.\n */\nre_frame.core.reg_global_interceptor = (function re_frame$core$reg_global_interceptor(interceptor){\nreturn re_frame.settings.reg_global_interceptor(interceptor);\n});\n/**\n * Unregisters global interceptors (presumably registered previously via the use of `reg-global-interceptor`). \n * \n *   When called with no args, it will unregister all currently registered global interceptors. \n * \n *   When given one arg, assumed to be the `id` of a previously registered \n *   global interceptors, it will unregister the associated interceptor. Will produce a warning to \n *   console if it finds no matching registration.\n */\nre_frame.core.clear_global_interceptor = (function re_frame$core$clear_global_interceptor(var_args){\nvar G__49335 = arguments.length;\nswitch (G__49335) {\ncase 0:\nreturn re_frame.core.clear_global_interceptor.cljs$core$IFn$_invoke$arity$0();\n\nbreak;\ncase 1:\nreturn re_frame.core.clear_global_interceptor.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.clear_global_interceptor.cljs$core$IFn$_invoke$arity$0 = (function (){\nreturn re_frame.settings.clear_global_interceptors.cljs$core$IFn$_invoke$arity$0();\n}));\n\n(re_frame.core.clear_global_interceptor.cljs$core$IFn$_invoke$arity$1 = (function (id){\nreturn re_frame.settings.clear_global_interceptors.cljs$core$IFn$_invoke$arity$1(id);\n}));\n\n(re_frame.core.clear_global_interceptor.cljs$lang$maxFixedArity = 1);\n\n/**\n * A utility function for creating interceptors.\n * \n *   Accepts three optional, named arguments:\n * \n *   - `:id` - an id for the interceptor (decorative only)\n *   - `:before` - the interceptor's before function\n *   - `:after`  - the interceptor's after function\n * \n *   Example use:\n * \n *    (def my-interceptor\n *      (->interceptor\n *       :id     :my-interceptor\n *       :before (fn [context]\n *                 ... modifies and returns `context`)\n *       :after  (fn [context] \n *                 ... modifies and returns `context`)))\n * \n *   Notes:\n *   \n *  - `:before` functions modify and return their `context` argument. Sometimes they \n *    only side effect, in which case, they'll perform the side effect and return\n *    `context` unchanged.\n *  - `:before` functions often modify the `:coeffects` map within `context` and, \n *    if they do, then they should use the utility functions `get-coeffect` and \n *    `assoc-coeffect`.\n *  - `:after` functions modify and return their `context` argument. Sometimes they \n *    only side effect, in which case, they'll perform the side effect and return \n *    `context` unchanged.\n *  - `:after` functions often modify the `:effects` map within `context` and, \n *    if they do, then they should use the utility functions `get-effect`\n *    and `assoc-effect`\n */\nre_frame.core.__GT_interceptor = (function re_frame$core$__GT_interceptor(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49513 = arguments.length;\nvar i__4737__auto___49514 = (0);\nwhile(true){\nif((i__4737__auto___49514 < len__4736__auto___49513)){\nargs__4742__auto__.push((arguments[i__4737__auto___49514]));\n\nvar G__49518 = (i__4737__auto___49514 + (1));\ni__4737__auto___49514 = G__49518;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((0) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((0)),(0),null)):null);\nreturn re_frame.core.__GT_interceptor.cljs$core$IFn$_invoke$arity$variadic(argseq__4743__auto__);\n});\n\n(re_frame.core.__GT_interceptor.cljs$core$IFn$_invoke$arity$variadic = (function (p__49340){\nvar map__49341 = p__49340;\nvar map__49341__$1 = (((((!((map__49341 == null))))?(((((map__49341.cljs$lang$protocol_mask$partition0$ & (64))) || ((cljs.core.PROTOCOL_SENTINEL === map__49341.cljs$core$ISeq$))))?true:false):false))?cljs.core.apply.cljs$core$IFn$_invoke$arity$2(cljs.core.hash_map,map__49341):map__49341);\nvar m = map__49341__$1;\nvar id = cljs.core.get.cljs$core$IFn$_invoke$arity$2(map__49341__$1,new cljs.core.Keyword(null,\"id\",\"id\",-1388402092));\nvar before = cljs.core.get.cljs$core$IFn$_invoke$arity$2(map__49341__$1,new cljs.core.Keyword(null,\"before\",\"before\",-1633692388));\nvar after = cljs.core.get.cljs$core$IFn$_invoke$arity$2(map__49341__$1,new cljs.core.Keyword(null,\"after\",\"after\",594996914));\nreturn re_frame.utils.apply_kw.cljs$core$IFn$_invoke$arity$variadic(re_frame.interceptor.__GT_interceptor,cljs.core.prim_seq.cljs$core$IFn$_invoke$arity$2([m], 0));\n}));\n\n(re_frame.core.__GT_interceptor.cljs$lang$maxFixedArity = (0));\n\n/** @this {Function} */\n(re_frame.core.__GT_interceptor.cljs$lang$applyTo = (function (seq49338){\nvar self__4724__auto__ = this;\nreturn self__4724__auto__.cljs$core$IFn$_invoke$arity$variadic(cljs.core.seq(seq49338));\n}));\n\n/**\n * A utility function, typically used when writing an interceptor's `:before` function.\n * \n * When called with one argument, it returns the `:coeffects` map from with that `context`.\n * \n * When called with two or three arguments, behaves like `clojure.core/get` and\n * returns the value mapped to `key` in the `:coeffects` map within `context`, `not-found` or\n * `nil` if `key` is not present.\n */\nre_frame.core.get_coeffect = (function re_frame$core$get_coeffect(var_args){\nvar G__49346 = arguments.length;\nswitch (G__49346) {\ncase 1:\nreturn re_frame.core.get_coeffect.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ncase 2:\nreturn re_frame.core.get_coeffect.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ncase 3:\nreturn re_frame.core.get_coeffect.cljs$core$IFn$_invoke$arity$3((arguments[(0)]),(arguments[(1)]),(arguments[(2)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.get_coeffect.cljs$core$IFn$_invoke$arity$1 = (function (context){\nreturn re_frame.interceptor.get_coeffect.cljs$core$IFn$_invoke$arity$1(context);\n}));\n\n(re_frame.core.get_coeffect.cljs$core$IFn$_invoke$arity$2 = (function (context,key){\nreturn re_frame.interceptor.get_coeffect.cljs$core$IFn$_invoke$arity$2(context,key);\n}));\n\n(re_frame.core.get_coeffect.cljs$core$IFn$_invoke$arity$3 = (function (context,key,not_found){\nreturn re_frame.interceptor.get_coeffect.cljs$core$IFn$_invoke$arity$3(context,key,not_found);\n}));\n\n(re_frame.core.get_coeffect.cljs$lang$maxFixedArity = 3);\n\n/**\n * A utility function, typically used when writing an interceptor's `:before` function.\n * \n * Adds or updates a key/value pair in the `:coeffects` map within `context`. \n */\nre_frame.core.assoc_coeffect = (function re_frame$core$assoc_coeffect(context,key,value){\nreturn re_frame.interceptor.assoc_coeffect(context,key,value);\n});\n/**\n * A utility function, used when writing interceptors, typically within an `:after` function.\n * \n * When called with one argument, returns the `:effects` map from the `context`.\n * \n * When called with two or three arguments, behaves like `clojure.core/get` and\n * returns the value mapped to `key` in the effects map, `not-found` or\n * `nil` if `key` is not present.\n */\nre_frame.core.get_effect = (function re_frame$core$get_effect(var_args){\nvar G__49362 = arguments.length;\nswitch (G__49362) {\ncase 1:\nreturn re_frame.core.get_effect.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ncase 2:\nreturn re_frame.core.get_effect.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ncase 3:\nreturn re_frame.core.get_effect.cljs$core$IFn$_invoke$arity$3((arguments[(0)]),(arguments[(1)]),(arguments[(2)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.get_effect.cljs$core$IFn$_invoke$arity$1 = (function (context){\nreturn re_frame.interceptor.get_effect.cljs$core$IFn$_invoke$arity$1(context);\n}));\n\n(re_frame.core.get_effect.cljs$core$IFn$_invoke$arity$2 = (function (context,key){\nreturn re_frame.interceptor.get_effect.cljs$core$IFn$_invoke$arity$2(context,key);\n}));\n\n(re_frame.core.get_effect.cljs$core$IFn$_invoke$arity$3 = (function (context,key,not_found){\nreturn re_frame.interceptor.get_effect.cljs$core$IFn$_invoke$arity$3(context,key,not_found);\n}));\n\n(re_frame.core.get_effect.cljs$lang$maxFixedArity = 3);\n\n/**\n * A utility function, typically used when writing an interceptor's `:after` function.\n * \n * Adds or updates a key/value pair in the `:effects` map within `context`. \n */\nre_frame.core.assoc_effect = (function re_frame$core$assoc_effect(context,key,value){\nreturn re_frame.interceptor.assoc_effect(context,key,value);\n});\n/**\n * A utility function, used when writing an interceptor's `:before` function.\n * \n *   Adds the given collection of `interceptors` to those already in `context's` \n *   execution `:queue`. It returns the updated `context`.\n * \n *   So, it provides a way for one Interceptor to add more interceptors to the \n *   currently executing interceptor chain.\n *   \n */\nre_frame.core.enqueue = (function re_frame$core$enqueue(context,interceptors){\nreturn re_frame.interceptor.enqueue(context,interceptors);\n});\n/**\n * re-frame outputs warnings and errors via the API function `console` \n * which, by default, delegates to `js/console`'s default implementation for \n *   `log`, `error`, `warn`, `debug`, `group` and `groupEnd`. But, using this function,\n * you can override that behaviour with your own functions. \n * \n *   The argument `new-loggers` should be a map containing a subset of they keys \n *   for the standard `loggers`, namely  `:log` `:error` `:warn` `:debug` `:group` \n *   or `:groupEnd`.\n * \n *   Example Usage:\n * \n *    (defn my-logger      ;; my alternative logging function\n *      [& args]\n *      (post-it-somewhere (apply str args)))\n * \n *    ;; now install my alternative loggers\n *    (re-frame.core/set-loggers!  {:warn my-logger :log my-logger})\n * \n */\nre_frame.core.set_loggers_BANG_ = (function re_frame$core$set_loggers_BANG_(new_loggers){\nreturn re_frame.loggers.set_loggers_BANG_(new_loggers);\n});\n/**\n * A utility logging function which is used internally within re-frame to produce \n *   warnings and other output. It can also be used by libraries which \n *   extend re-frame, such as effect handlers.\n * \n *   By default, it will output the given `args` to `js/console` at the given log `level`.\n *   However, an application using re-frame can redirect `console` output via `set-loggers!`. \n * \n *   `level` can be one of `:log`, `:error`, `:warn`, `:debug`, `:group` or `:groupEnd`.\n * \n *   Example usage:\n * \n *    (console :error \"Sure enough it happened:\" a-var \"and\" another)\n *    (console :warn \"Possible breach of containment wall at:\" dt)\n *   \n */\nre_frame.core.console = (function re_frame$core$console(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49546 = arguments.length;\nvar i__4737__auto___49547 = (0);\nwhile(true){\nif((i__4737__auto___49547 < len__4736__auto___49546)){\nargs__4742__auto__.push((arguments[i__4737__auto___49547]));\n\nvar G__49548 = (i__4737__auto___49547 + (1));\ni__4737__auto___49547 = G__49548;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((1) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((1)),(0),null)):null);\nreturn re_frame.core.console.cljs$core$IFn$_invoke$arity$variadic((arguments[(0)]),argseq__4743__auto__);\n});\n\n(re_frame.core.console.cljs$core$IFn$_invoke$arity$variadic = (function (level,args){\nreturn cljs.core.apply.cljs$core$IFn$_invoke$arity$2(re_frame.loggers.console,cljs.core.into.cljs$core$IFn$_invoke$arity$2(new cljs.core.PersistentVector(null, 1, 5, cljs.core.PersistentVector.EMPTY_NODE, [level], null),args));\n}));\n\n(re_frame.core.console.cljs$lang$maxFixedArity = (1));\n\n/** @this {Function} */\n(re_frame.core.console.cljs$lang$applyTo = (function (seq49371){\nvar G__49372 = cljs.core.first(seq49371);\nvar seq49371__$1 = cljs.core.next(seq49371);\nvar self__4723__auto__ = this;\nreturn self__4723__auto__.cljs$core$IFn$_invoke$arity$variadic(G__49372,seq49371__$1);\n}));\n\n/**\n * This is a utility function, typically used in testing.\n * \n *   It checkpoints the current state of re-frame and returns a function which, when\n *   later called, will restore re-frame to the checkpointed state.\n * \n *   The checkpoint includes `app-db`, all registered handlers and all subscriptions.\n *   \n */\nre_frame.core.make_restore_fn = (function re_frame$core$make_restore_fn(){\nvar handlers = cljs.core.deref(re_frame.registrar.kind__GT_id__GT_handler);\nvar app_db = cljs.core.deref(re_frame.db.app_db);\nvar subs_cache = cljs.core.deref(re_frame.subs.query__GT_reaction);\nreturn (function (){\nvar original_subs_49551 = cljs.core.set(cljs.core.vals(subs_cache));\nvar current_subs_49552 = cljs.core.set(cljs.core.vals(cljs.core.deref(re_frame.subs.query__GT_reaction)));\nvar seq__49381_49553 = cljs.core.seq(clojure.set.difference.cljs$core$IFn$_invoke$arity$2(current_subs_49552,original_subs_49551));\nvar chunk__49382_49554 = null;\nvar count__49383_49555 = (0);\nvar i__49384_49556 = (0);\nwhile(true){\nif((i__49384_49556 < count__49383_49555)){\nvar sub_49557 = chunk__49382_49554.cljs$core$IIndexed$_nth$arity$2(null,i__49384_49556);\nre_frame.interop.dispose_BANG_(sub_49557);\n\n\nvar G__49558 = seq__49381_49553;\nvar G__49559 = chunk__49382_49554;\nvar G__49560 = count__49383_49555;\nvar G__49561 = (i__49384_49556 + (1));\nseq__49381_49553 = G__49558;\nchunk__49382_49554 = G__49559;\ncount__49383_49555 = G__49560;\ni__49384_49556 = G__49561;\ncontinue;\n} else {\nvar temp__5735__auto___49562 = cljs.core.seq(seq__49381_49553);\nif(temp__5735__auto___49562){\nvar seq__49381_49563__$1 = temp__5735__auto___49562;\nif(cljs.core.chunked_seq_QMARK_(seq__49381_49563__$1)){\nvar c__4556__auto___49566 = cljs.core.chunk_first(seq__49381_49563__$1);\nvar G__49567 = cljs.core.chunk_rest(seq__49381_49563__$1);\nvar G__49568 = c__4556__auto___49566;\nvar G__49569 = cljs.core.count(c__4556__auto___49566);\nvar G__49570 = (0);\nseq__49381_49553 = G__49567;\nchunk__49382_49554 = G__49568;\ncount__49383_49555 = G__49569;\ni__49384_49556 = G__49570;\ncontinue;\n} else {\nvar sub_49571 = cljs.core.first(seq__49381_49563__$1);\nre_frame.interop.dispose_BANG_(sub_49571);\n\n\nvar G__49572 = cljs.core.next(seq__49381_49563__$1);\nvar G__49573 = null;\nvar G__49574 = (0);\nvar G__49575 = (0);\nseq__49381_49553 = G__49572;\nchunk__49382_49554 = G__49573;\ncount__49383_49555 = G__49574;\ni__49384_49556 = G__49575;\ncontinue;\n}\n} else {\n}\n}\nbreak;\n}\n\ncljs.core.reset_BANG_(re_frame.registrar.kind__GT_id__GT_handler,handlers);\n\ncljs.core.reset_BANG_(re_frame.db.app_db,app_db);\n\nreturn null;\n});\n});\n/**\n * Removes all events currently queued for processing\n */\nre_frame.core.purge_event_queue = (function re_frame$core$purge_event_queue(){\nreturn re_frame.router.event_queue.re_frame$router$IEventQueue$purge$arity$1(null);\n});\n/**\n * Registers the given function `f` to be called after each event is processed. \n * \n * `f` will be called with two arguments:\n * \n *  - `event`: a vector. The event just processed.\n *  - `queue`: a PersistentQueue, possibly empty, of events yet to be processed.\n * \n * This facility is useful in advanced cases like:\n * \n *   - you are implementing a complex bootstrap pipeline\n *   - you want to create your own handling infrastructure, with perhaps multiple\n *     handlers for the one event, etc.  Hook in here.\n *   - libraries providing 'isomorphic javascript' rendering on  Nodejs or Nashorn.\n * \n *   `id` is typically a keyword. If it supplied when an `f` is added, it can be \n *   subsequently be used to identify it for removal. See `remove-post-event-callback`.\n *   \n */\nre_frame.core.add_post_event_callback = (function re_frame$core$add_post_event_callback(var_args){\nvar G__49399 = arguments.length;\nswitch (G__49399) {\ncase 1:\nreturn re_frame.core.add_post_event_callback.cljs$core$IFn$_invoke$arity$1((arguments[(0)]));\n\nbreak;\ncase 2:\nreturn re_frame.core.add_post_event_callback.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)]));\n\nbreak;\ndefault:\nthrow (new Error([\"Invalid arity: \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(arguments.length)].join('')));\n\n}\n});\n\n(re_frame.core.add_post_event_callback.cljs$core$IFn$_invoke$arity$1 = (function (f){\nreturn re_frame.core.add_post_event_callback.cljs$core$IFn$_invoke$arity$2(f,f);\n}));\n\n(re_frame.core.add_post_event_callback.cljs$core$IFn$_invoke$arity$2 = (function (id,f){\nreturn re_frame.router.event_queue.re_frame$router$IEventQueue$add_post_event_callback$arity$3(null,id,f);\n}));\n\n(re_frame.core.add_post_event_callback.cljs$lang$maxFixedArity = 2);\n\n/**\n * Unregisters a post event callback function, identified by `id`. \n * \n *   Such a function must have been previously registered via `add-post-event-callback`\n */\nre_frame.core.remove_post_event_callback = (function re_frame$core$remove_post_event_callback(id){\nreturn re_frame.router.event_queue.re_frame$router$IEventQueue$remove_post_event_callback$arity$2(null,id);\n});\n/**\n * Deprecated. Use `reg-event-db` instead.\n */\nre_frame.core.register_handler = (function re_frame$core$register_handler(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49581 = arguments.length;\nvar i__4737__auto___49582 = (0);\nwhile(true){\nif((i__4737__auto___49582 < len__4736__auto___49581)){\nargs__4742__auto__.push((arguments[i__4737__auto___49582]));\n\nvar G__49583 = (i__4737__auto___49582 + (1));\ni__4737__auto___49582 = G__49583;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((0) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((0)),(0),null)):null);\nreturn re_frame.core.register_handler.cljs$core$IFn$_invoke$arity$variadic(argseq__4743__auto__);\n});\n\n(re_frame.core.register_handler.cljs$core$IFn$_invoke$arity$variadic = (function (args){\nre_frame.core.console.cljs$core$IFn$_invoke$arity$variadic(new cljs.core.Keyword(null,\"warn\",\"warn\",-436710552),cljs.core.prim_seq.cljs$core$IFn$_invoke$arity$2([\"re-frame: \\\"register-handler\\\" has been renamed \\\"reg-event-db\\\" (look for registration of \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(cljs.core.first(args)),\")\"], 0));\n\nreturn cljs.core.apply.cljs$core$IFn$_invoke$arity$2(re_frame.core.reg_event_db,args);\n}));\n\n(re_frame.core.register_handler.cljs$lang$maxFixedArity = (0));\n\n/** @this {Function} */\n(re_frame.core.register_handler.cljs$lang$applyTo = (function (seq49412){\nvar self__4724__auto__ = this;\nreturn self__4724__auto__.cljs$core$IFn$_invoke$arity$variadic(cljs.core.seq(seq49412));\n}));\n\n/**\n * Deprecated. Use `reg-sub-raw` instead.\n */\nre_frame.core.register_sub = (function re_frame$core$register_sub(var_args){\nvar args__4742__auto__ = [];\nvar len__4736__auto___49592 = arguments.length;\nvar i__4737__auto___49593 = (0);\nwhile(true){\nif((i__4737__auto___49593 < len__4736__auto___49592)){\nargs__4742__auto__.push((arguments[i__4737__auto___49593]));\n\nvar G__49594 = (i__4737__auto___49593 + (1));\ni__4737__auto___49593 = G__49594;\ncontinue;\n} else {\n}\nbreak;\n}\n\nvar argseq__4743__auto__ = ((((0) < args__4742__auto__.length))?(new cljs.core.IndexedSeq(args__4742__auto__.slice((0)),(0),null)):null);\nreturn re_frame.core.register_sub.cljs$core$IFn$_invoke$arity$variadic(argseq__4743__auto__);\n});\n\n(re_frame.core.register_sub.cljs$core$IFn$_invoke$arity$variadic = (function (args){\nre_frame.core.console.cljs$core$IFn$_invoke$arity$variadic(new cljs.core.Keyword(null,\"warn\",\"warn\",-436710552),cljs.core.prim_seq.cljs$core$IFn$_invoke$arity$2([\"re-frame: \\\"register-sub\\\" is used to register the event \",cljs.core.str.cljs$core$IFn$_invoke$arity$1(cljs.core.first(args)),\" but it is a deprecated part of the API. Please use \\\"reg-sub-raw\\\" instead.\"], 0));\n\nreturn cljs.core.apply.cljs$core$IFn$_invoke$arity$2(re_frame.core.reg_sub_raw,args);\n}));\n\n(re_frame.core.register_sub.cljs$lang$maxFixedArity = (0));\n\n/** @this {Function} */\n(re_frame.core.register_sub.cljs$lang$applyTo = (function (seq49427){\nvar self__4724__auto__ = this;\nreturn self__4724__auto__.cljs$core$IFn$_invoke$arity$variadic(cljs.core.seq(seq49427));\n}));\n\n","~:ns-info",["^ ","~:rename-macros",null,"~:renames",["^ "],"~:meta",["^ ","~:file","re_frame/core.cljc","~:line",1,"~:column",5,"~:end-line",1,"~:end-column",18],"~:ns-aliases",["^ ","~$cljs.loader","~$shadow.loader","~$clojure.pprint","~$cljs.pprint","~$react","~$shadow.js.shim.module$react","~$clojure.spec.alpha","~$cljs.spec.alpha"],"~:use-macros",null,"~:excludes",["~#set",[]],"~:name","~$re-frame.core","~:op","~:ns","~:imports",null,"~:requires",["^ ","~$re-frame.interop","^M","~$subs","~$re-frame.subs","~$set","~$clojure.set","~$cofx","~$re-frame.cofx","~$re-frame.interceptor","^T","~$fx","~$re-frame.fx","~$re-frame.events","^W","~$loggers","~$re-frame.loggers","~$re-frame.settings","^Z","^V","^V","~$re-frame.registrar","^[","~$cljs.core","^10","~$interceptor","^T","~$goog","^12","~$router","~$re-frame.router","~$db","~$re-frame.db","~$registrar","^[","^14","^14","~$re-frame.utils","^18","^Q","^Q","~$events","^W","~$settings","^Z","~$re-frame.std-interceptors","^1;","^Y","^Y","^O","^O","~$interop","^M","~$utils","^18","~$std-interceptors","^1;","^S","^S","^16","^16"],"~:seen",["^F",["~:require"]],"~:uses",["^ ","~$db-handler->interceptor","^1;","~$fx-handler->interceptor","^1;","~$ctx-handler->interceptor","^1;"],"~:require-macros",["^ ","^10","^10"],"~:form",["~#list",["~$ns","^H",["^1G",["^1@",["^W","~:as","^19"],["^O","^1I","^N"],["^M","^1I","^1<"],["^16","^1I","^15"],["^V","^1I","^U"],["^S","^1I","^R"],["^14","^1I","^13"],["^Z","^1I","^1:"],["^Y","^1I","^X"],["^[","^1I","^17"],["^T","^1I","^11"],["^1;","^1I","^1>","~:refer",["^1B","^1C","^1D"]],["^18","^1I","^1="],["^Q","^1I","^P"]]]]],"~:flags",["^ ","^1@",["^F",[]]],"~:js-deps",["^ "],"~:deps",["^12","^10","^W","^O","^M","^16","^V","^S","^14","^Z","^Y","^[","^T","^1;","^18","^Q"]],"^J","^H","~:resource-id",["~:shadow.build.classpath/resource","re_frame/core.cljc"],"~:compiled-at",1613924122517,"~:resource-name","re_frame/core.cljc","~:warnings",[],"~:source","(ns re-frame.core\n  (:require\n    [re-frame.events           :as events]\n    [re-frame.subs             :as subs]\n    [re-frame.interop          :as interop]\n    [re-frame.db               :as db]\n    [re-frame.fx               :as fx]\n    [re-frame.cofx             :as cofx]\n    [re-frame.router           :as router]\n    [re-frame.settings         :as settings]\n    [re-frame.loggers          :as loggers]\n    [re-frame.registrar        :as registrar]\n    [re-frame.interceptor      :as interceptor]\n    [re-frame.std-interceptors :as std-interceptors :refer [db-handler->interceptor\n                                                             fx-handler->interceptor\n                                                             ctx-handler->interceptor]]\n    [re-frame.utils            :as utils]\n    [clojure.set               :as set]))\n\n\n;; -- dispatch ----------------------------------------------------------------\n\n(defn dispatch\n  \"Queue `event` for processing (handling). \n\n  `event` is a vector and the first element is typically a keyword\n  which identifies the kind of event.\n\n  The event will be added to a FIFO processing queue, so event\n  handling does not happen immediately. It will happen 'very soon'\n  bit not now. And if the queue already contains events, they\n  will be processed first.\n\n  Usage:\n      \n      (dispatch [:order \\\"pizza\\\" {:supreme 2 :meatlovers 1 :veg 1}])\n  \"\n  [event]\n  (router/dispatch event))\n\n(defn dispatch-sync\n  \"Synchronously (immediately) process `event`. It does **not** queue\n  the event for handling later as `dispatch` does. \n  \n  `event` is a vector and the first element is typically a keyword \n  which identifies the kind of event.\n\n  It is an error to use `dispatch-sync` within an event handler because \n  you can't immediately process an new event when one is already\n  part way through being processed.\n\n  Generally, avoid using this function, and instead, use `dispatch`. \n  Only use it in the narrow set of cases where any delay in \n  processing is a problem:\n\n    1. the `:on-change` handler of a text field where we are expecting fast typing\n    2. when initialising your app - see 'main' in examples/todomvc/src/core.cljs\n    3. in a unit test where immediate, synchronous processing is useful\n\n  Usage:\n\n      (dispatch-sync [:sing :falsetto \\\"piano accordion\\\"])\n  \"\n  [event]\n  (router/dispatch-sync event))\n\n\n;; -- subscriptions -----------------------------------------------------------\n(defn reg-sub\n  \"A call to `reg-sub` associates a `query-id` WITH two functions.\n   \n  The two functions provide 'a mechanism' for creating a node \n  in the Signal Graph. When a node of type `query-id` is needed, \n  the two functions can be used to create it.\n  \n  The three arguments are: \n   \n  - `query-id` - typically a namespaced keyword (later used in subscribe)\n  - optionally, an `input signals` function which returns the input data\n    flows required by this kind of node. \n  - a `computation function` which computes the value (output) of the \n    node (from the input data flows)\n     \n  Later, during app execution, a call to `(subscribe [:sub-id 3 :blue])`,\n  will trigger the need for a new `:sub-id` Signal Graph node (matching the \n  query `[:sub-id 3 :blue]`). And, to create that node the two functions \n  associated with `:sub-id` will be looked up and used.\n\n  Just to be clear: calling `reg-sub` does not immediately create a node. \n  It only registers 'a mechanism' (the two functions) by which nodes \n  can be created later, when a node is bought into existence by the \n  use of `subscribe` in a `View Function`.\n\n  The `computation function` is expected to take two arguments:\n  \n    - `input-values` - the values which flow into this node (how is it wierd into the graph?)\n    - `query-vector` - the vector given to `subscribe`\n  \n  and it returns a computed value (which then becomes the output of the node)\n\n  When `computation function` is called, the 2nd `query-vector` argument will be that \n  vector supplied to the `subscribe`. So, if the call was `(subscribe [:sub-id 3 :blue])`,\n  then the `query-vector` supplied to the computaton function will be `[:sub-id 3 :blue]`.\n\n  The argument(s) supplied to `reg-sub` between `query-id` and the `computation-function` \n  can vary in 3 ways, but whatever is there defines the `input signals` part \n  of `the mechanism`, specifying what input values \\\"flow into\\\" the \n  `computation function` (as the 1st argument) when it is called.\n\n  So, `reg-sub` can be called in one of three ways, because there are three ways \n  to define the input signals part. But note, the 2nd method, in which a \n  `signals function` is explicitly supplied, is the most canonical and \n  instructive. The other two are really just sugary variations.\n\n  **First variation** - no input signal function given:\n\n      (reg-sub\n        :query-id\n        a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n     In the absence of an explicit `signals function`, the node's input signal defaults to `app-db`\n     and, as a result, the value within `app-db` (a map) is\n     is given as the 1st argument when `a-computation-fn` is called.\n\n\n  **Second variation** - a signal function is explicitly supplied:\n\n      (reg-sub\n        :query-id\n        signal-fn     ;; <-- here\n        computation-fn)\n\n  This is the most canonical and instructive of the three variations.\n\n  When a node is created from the template, the `signal function` will be called and it\n  is expected to return the input signal(s) as either a singleton, if there is only\n  one, or a sequence if there are many, or a map with the signals as the values.\n\n  The current values of the returned signals will be supplied as the 1st argument to\n  the `a-computation-fn` when it is called - and subject to what this `signal-fn` returns,\n  this value will be either a singleton, sequence or map of them (paralleling\n  the structure returned by the `signal function`).\n\n  This example `signal function` returns a 2-vector of input signals.\n\n      (fn [query-vec dynamic-vec]\n         [(subscribe [:a-sub])\n          (subscribe [:b-sub])])\n\n  The associated computation function must be written\n  to expect a 2-vector of values for its first argument:\n\n      (fn [[a b] query-vec]     ;; 1st argument is a seq of two values\n        ....)\n\n  If, on the other hand, the signal function was simpler and returned a singleton, like this:\n\n     (fn [query-vec dynamic-vec]\n       (subscribe [:a-sub]))      ;; <-- returning a singleton\n\n  then the associated computation function must be written to expect a single value\n  as the 1st argument:\n\n      (fn [a query-vec]       ;; 1st argument is a single value\n         ...)\n\n  Further Note: variation #1 above, in which an `input-fn` was not supplied, like this:\n\n      (reg-sub\n        :query-id\n        a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n  is the equivalent of using this\n  2nd variation and explicitly suppling a `signal-fn` which returns `app-db`:\n\n      (reg-sub\n        :query-id\n        (fn [_ _]  re-frame/app-db)   ;; <--- explicit signal-fn\n        a-computation-fn)             ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n  **Third variation** - syntax Sugar\n\n      (reg-sub\n        :a-b-sub\n        :<- [:a-sub]\n        :<- [:b-sub]\n        (fn [[a b] query-vec]    ;; 1st argument is a seq of two values\n          {:a a :b b}))\n\n  This 3rd variation is just syntactic sugar for the 2nd.  Instead of providing an\n  `signals-fn` you provide one or more pairs of `:<-` and a subscription vector.\n\n  If you supply only one pair a singleton will be supplied to the computation function,\n  as if you had supplied a `signal-fn` returning only a single value:\n\n\n      (reg-sub\n        :a-sub\n        :<- [:a-sub]\n        (fn [a query-vec]      ;; only one pair, so 1st argument is a single value\n          ...))\n\n  For further understanding, read the tutorials, and look at the detailed comments in\n  /examples/todomvc/src/subs.cljs.\n        \n  See also: `subscribe`\n  \"\n  [query-id & args]\n  (apply subs/reg-sub (into [query-id] args)))\n\n(defn subscribe\n  \"Given a `query` vector, returns a Reagent `reaction` which will, over\n  time, reactively deliver a stream of values. So, in FRP-ish terms,\n  it returns a `Signal`.\n\n  To obtain the current value from the Signal, it must be dereferenced: \n  \n      (let [signal (subscribe [:items])\n            value  (deref signal)]     ;; could be written as @signal\n        ...)\n   \n   which is typically written tersely as simple:\n   \n      (let [items  @(subscribe [:items])] \n        ...)\n      \n\n  `query` is a vector of at least one element. The first element is the\n  `query-id`, typically a namespaced keyword. The rest of the vector's\n  elements are optional, additional values which parameterise the query\n  performed.\n\n  `dynv` is an optional 3rd argument, which is a vector of further input\n  signals (atoms, reactions, etc), NOT values. This argument exists for\n  historical reasons and is borderline deprecated these days.\n\n  **Example Usage**:\n\n      (subscribe [:items])\n      (subscribe [:items \\\"blue\\\" :small])\n      (subscribe [:items {:colour \\\"blue\\\"  :size :small}])\n \n  Note: for any given call to `subscribe` there must have been a previous call\n  to `reg-sub`, registering the query handler (functions) associated with \n  `query-id`.\n\n  **Hint**\n\n  When used in a view function BE SURE to `deref` the returned value.\n  In fact, to avoid any mistakes, some prefer to define:\n  \n      (def <sub  (comp deref re-frame.core/subscribe))\n \n  And then, within their views, they call  `(<sub [:items :small])` rather\n  than using `subscribe` directly.\n\n  **De-duplication**\n\n  Two, or more, concurrent subscriptions for the same query will \n  source reactive updates from the one executing handler.\n      \n  See also: `reg-sub`\n  \"\n  ([query]\n   (subs/subscribe query))\n  ([query dynv]\n   (subs/subscribe query dynv)))\n\n(defn clear-sub ;; think unreg-sub\n  \"Unregisters subscription handlers (presumably registered previously via the use of `reg-sub`). \n   \n  When called with no args, it will unregister all currently registered subscription handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  subscription handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\n\n  NOTE: Depending on the usecase, it may be necessary to call `clear-subscription-cache!` afterwards\"\n  ([]\n   (registrar/clear-handlers subs/kind))\n  ([query-id]\n   (registrar/clear-handlers subs/kind query-id)))\n\n\n(defn clear-subscription-cache!\n  \"Removes all subscriptions from the cache.\n\n  This function can be used at development time or test time. Useful when hot realoding\n  namespaces containing subscription handlers. Also call it after a React/render exception,\n  because React components won't have been cleaned up properly. And this, in turn, means \n  the subscriptions within those components won't have been cleaned up correctly. So this \n  forces the issue.\n  \"\n  []\n  (subs/clear-subscription-cache!))\n\n(defn reg-sub-raw\n  \"This is a low level, advanced function.  You should probably be\n  using `reg-sub` instead.\n\n  Some explanation is available in the docs at\n  <a href=\\\"http://day8.github.io/re-frame/flow-mechanics/\\\" target=\\\"_blank\\\">http://day8.github.io/re-frame/flow-mechanics/</a>\"\n  [query-id handler-fn]\n  (registrar/register-handler subs/kind query-id handler-fn))\n\n\n;; -- effects -----------------------------------------------------------------\n(defn reg-fx\n  \"Register the given effect `handler` for the given `id`:\n\n    - `id` is keyword, often namespaced.\n    - `handler` is a side-effecting function which takes a single argument and whose return\n      value is ignored.\n\n  To use, first, associate `:effect2` with a handler:\n\n      (reg-fx\n         :effect2\n         (fn [value]\n            ... do something side-effect-y))\n\n  Then, later, if an event handler were to return this effects map:\n\n      {:effect2  [1 2]}\n\n  then the `handler` `fn` we registered previously, using `reg-fx`, will be\n  called with an argument of `[1 2]`.\n  \"\n  [id handler]\n  (fx/reg-fx id handler))\n\n\n(defn clear-fx ;; think unreg-fx\n  \"Unregisters effect handlers (presumably registered previously via the use of `reg-fx`). \n   \n  When called with no args, it will unregister all currently registered effect handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  effect handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\n  \"\n  ([]\n   (registrar/clear-handlers fx/kind))\n  ([id]\n   (registrar/clear-handlers fx/kind id)))\n\n;; -- coeffects ---------------------------------------------------------------\n(defn reg-cofx\n  \"Register the given coeffect `handler` for the given `id`, for later use\n  within `inject-cofx`:\n\n    - `id` is keyword, often namespaced.\n    - `handler` is a function which takes either one or two arguements, the first of which is\n       always `coeffects` and which returns an updated `coeffects`.\n\n  See also: `inject-cofx` \n  \"\n  [id handler]\n  (cofx/reg-cofx id handler))\n\n(defn inject-cofx\n  \"Given an `id`, and an optional, arbitrary `value`, returns an interceptor\n  whose `:before` adds to the `:coeffects` (map) by calling a pre-registered\n  'coeffect handler' identified by the `id`.\n\n  The previous association of a `coeffect handler` with an `id` will have\n  happened via a call to `re-frame.core/reg-cofx` - generally on program startup.\n\n  Within the created interceptor, this 'looked up' `coeffect handler` will\n  be called (within the `:before`) with two arguments:\n\n  - the current value of `:coeffects`\n  - optionally, the originally supplied arbitrary `value`\n\n  This `coeffect handler` is expected to modify and return its first, `coeffects` argument.\n\n  **Example of `inject-cofx` and `reg-cofx` working together**\n\n\n  First - Early in app startup, you register a `coeffect handler` for `:datetime`:\n\n      (re-frame.core/reg-cofx\n        :datetime                        ;; usage  (inject-cofx :datetime)\n        (fn coeffect-handler\n          [coeffect]\n          (assoc coeffect :now (js/Date.))))   ;; modify and return first arg\n\n  Second - Later, add an interceptor to an -fx event handler, using `inject-cofx`:\n\n      (re-frame.core/reg-event-fx            ;; when registering an event handler\n        :event-id\n        [ ... (inject-cofx :datetime) ... ]  ;; <-- create an injecting interceptor\n        (fn event-handler\n          [coeffect event]\n            ;;... in here can access (:now coeffect) to obtain current datetime ... \n          )))\n\n  **Background**\n\n  `coeffects` are the input resources required by an event handler\n  to perform its job. The two most obvious ones are `db` and `event`.\n  But sometimes an event handler might need other resources.\n\n  Perhaps an event handler needs a random number or a GUID or the current\n  datetime. Perhaps it needs access to a DataScript database connection.\n\n  If an event handler directly accesses these resources, it stops being\n  pure and, consequently, it becomes harder to test, etc. So we don't\n  want that.\n\n  Instead, the interceptor created by this function is a way to 'inject'\n  'necessary resources' into the `:coeffects` (map) subsequently given\n  to the event handler at call time.\n          \n  See also `reg-cofx`\n  \"\n  ([id]\n   (cofx/inject-cofx id))\n  ([id value]\n   (cofx/inject-cofx id value)))\n\n(defn clear-cofx ;; think unreg-cofx\n  \"Unregisters coeffect handlers (presumably registered previously via the use of `reg-cofx`). \n   \n  When called with no args, it will unregister all currently registered coeffect handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  coeffect handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\"\n  ([]\n   (registrar/clear-handlers cofx/kind))\n  ([id]\n   (registrar/clear-handlers cofx/kind id)))\n\n;; -- Events ------------------------------------------------------------------\n\n(defn reg-event-db\n  \"Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n\n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (db event) -> db\n    - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n\n  Example Usage:\n\n      (reg-event-db \n        :token \n        (fn [db event]\n          (assoc db :some-key (get event 2)))  ;; return updated db\n\n  Or perhaps:\n\n      (reg-event-db\n        :namespaced/id           ;; <-- namespaced keywords are often used\n        [one two three]          ;; <-- a seq of interceptors\n        (fn [db [_ arg1 arg2]]   ;; <-- event vector is destructured\n          (-> db \n            (dissoc arg1)\n            (update :key + arg2))))   ;; return updated db\n  \"\n  ([id handler]\n   (reg-event-db id nil handler))\n  ([id interceptors handler]\n   (events/register id [cofx/inject-db fx/do-fx std-interceptors/inject-global-interceptors interceptors (db-handler->interceptor handler)])))\n\n\n(defn reg-event-fx\n  \"Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n\n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (coeffects-map event-vector) -> effects-map\n    - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n\n\n  Example Usage:\n\n      (reg-event-fx \n        :token \n        (fn [cofx event]\n          {:db (assoc (:db cofx) :some-key (get event 2))}))   ;; return a map of effects\n\n\n  Or perhaps:\n\n      (reg-event-fx\n        :namespaced/id           ;; <-- namespaced keywords are often used\n        [one two three]          ;; <-- a seq of interceptors\n        (fn [{:keys [db] :as cofx} [_ arg1 arg2]] ;; destructure both arguments\n          {:db       (assoc db :some-key arg1)          ;; return a map of effects\n           :dispatch [:some-event arg2]}))\n  \"\n  ([id handler]\n   (reg-event-fx id nil handler))\n  ([id interceptors handler]\n   (events/register id [cofx/inject-db fx/do-fx std-interceptors/inject-global-interceptors interceptors (fx-handler->interceptor handler)])))\n\n\n(defn reg-event-ctx\n  \"Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n   \n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (context-map event-vector) -> context-map\n\n  This form of registration is seldomAt dinner wenever used.\n  \"\n  ([id handler]\n   (reg-event-ctx id nil handler))\n  ([id interceptors handler]\n   (events/register id [cofx/inject-db fx/do-fx std-interceptors/inject-global-interceptors interceptors (ctx-handler->interceptor handler)])))\n\n(defn clear-event\n  \"Unregisters event handlers (presumably registered previously via the use of `reg-event-db` or `reg-event-fx`). \n   \n  When called with no args, it will unregister all currently registered event handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  event handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\"\n  ([]\n   (registrar/clear-handlers events/kind))\n  ([id]\n   (registrar/clear-handlers events/kind id)))\n\n;; -- interceptors ------------------------------------------------------------\n\n(def debug\n  \"An interceptor which logs/instruments an event handler's actions to\n  `js/console.debug`. See examples/todomvc/src/events.cljs for use.\n\n  Output includes:\n\n    1. the event vector\n    2. a `clojure.data/diff` of db, before vs after, which shows\n       the changes caused by the event handler. To understand the output,\n       you should understand:\n       <a href=\\\"https://clojuredocs.org/clojure.data/diff\\\" target=\\\"_blank\\\">https://clojuredocs.org/clojure.data/diff</a>.\n\n  You'd typically include this interceptor after (to the right of) any\n  `path` interceptor.\n\n  Warning:  calling `clojure.data/diff` on large, complex data structures\n  can be slow. So, you won't want this interceptor present in production\n  code. So, you should condition it out like this:\n\n      (re-frame.core/reg-event-db\n        :evt-id\n        [(when ^boolean goog.DEBUG re-frame.core/debug)]  ;; <-- conditional\n        (fn [db v]\n           ...))\n\n  To make this code fragment work, you'll also have to set `goog.DEBUG` to\n  `false` in your production builds. For an example, look in `project.clj` of /examples/todomvc.\n  \"\n  std-interceptors/debug)\n\n(defn path\n  \"Returns an interceptor which acts somewhat like `clojure.core/update-in`, in the sense that \n  the event handler is given a specific part of `app-db` to change, not all of `app-db`. \n   \n  The interceptor has both a `:before` and `:after` functions. The `:before` replaces  \n  the `:db` key within coeffects with a sub-path within `app-db`. The `:after` reverses the process, \n  and it grafts the handler's return value back into db, at the right path.\n\n  Examples:\n\n      (path :some :path)\n      (path [:some :path])\n      (path [:some :path] :to :here)\n      (path [:some :path] [:to] :here)\n\n  Example Use:\n\n      (reg-event-db\n        :event-id\n        (path [:a :b])  ;; <-- used here, in interceptor chain\n        (fn [b v]       ;; 1st arg is not db. Is the value from path [:a :b] within db\n          ... new-b))   ;; returns a new value for that path (not the entire db)\n\n  Notes:\n  \n    1. `path` may appear more than once in an interceptor chain. Progressive narrowing.\n    2. if `:effects` contains no `:db` effect, can't graft a value back in.\n  \"\n  [& args]\n  (apply std-interceptors/path args))\n\n(defn enrich\n  \"Returns an Interceptor which will run the given function `f` in the `:after`\n  position.  \n   \n  `f` is called with two arguments: `db` and `v`, and is expected to\n  return a modified `db`.\n\n  Unlike the `after` interceptor which is only about side effects, `enrich`\n  expects `f` to process and alter the given `db` coeffect in some useful way,\n  contributing to the derived data, flowing vibe.\n\n  #### Example Use:\n\n  Imagine that todomvc needed to do duplicate detection - if any two todos had\n  the same text, then highlight their background, and report them via a warning\n  at the bottom of the panel.\n\n  Almost any user action (edit text, add new todo, remove a todo) requires a\n  complete reassessment of duplication errors and warnings. Eg: that edit\n  just made might have introduced a new duplicate, or removed one. Same with\n  any todo removal. So we need to re-calculate warnings after any CRUD events\n  associated with the todos list.\n\n  Unless we are careful, we might end up coding subtly different checks\n  for each kind of CRUD operation.  The duplicates check made after\n  'delete todo' event might be subtly different to that done after an\n  editing operation. Nice and efficient, but fiddly. A bug generator\n  approach.\n\n  So, instead, we create an `f` which recalculates ALL warnings from scratch\n  every time there is ANY change. It will inspect all the todos, and\n  reset ALL FLAGS every time (overwriting what was there previously)\n  and fully recalculate the list of duplicates (displayed at the bottom?).\n\n  <a href=\\\"https://twitter.com/nathanmarz/status/879722740776939520\\\" target=\\\"_blank\\\">https://twitter.com/nathanmarz/status/879722740776939520</a>\n\n  By applying `f` in an `:enrich` interceptor, after every CRUD event,\n  we keep the handlers simple and yet we ensure this important step\n  (of getting warnings right) is not missed on any change.\n\n  We can test `f` easily - it is a pure function - independently of\n  any CRUD operation.\n\n  This brings huge simplicity at the expense of some re-computation\n  each time. This may be a very satisfactory trade-off in many cases.\"\n  [f]\n  (std-interceptors/enrich f))\n\n(def trim-v\n  \"An interceptor which removes the first element of the event vector,\n  before it is supplied to the event handler, allowing you to write more\n   aesthetically pleasing event handlers. No leading underscore on the event-v!\n\n  Your event handlers will look like this:\n\n      (reg-event-db\n        :event-id\n        [... trim-v ...]    ;; <-- added to the interceptors\n        (fn [db [x y z]]    ;; <-- instead of [_ x y z]\n          ...)\n    \"\n  std-interceptors/trim-v)\n\n(defn after\n  \"Returns an interceptor which runs the given function `f` in the `:after`\n  position, presumably for side effects.\n\n  `f` is called with two arguments: the `:effects` value for `:db`\n  (or the `:coeffect` value of `:db` if no `:db` effect is returned) and the event.\n  Its return value is ignored, so `f` can only side-effect.\n\n  An example of use can be seen in the re-frame github repo in `/examples/todomvc/events.cljs`:\n\n     - `f` runs schema validation (reporting any errors found).\n     - `f` writes to localstorage.\"\n  [f]\n  (std-interceptors/after f))\n\n(defn on-changes\n  \"Returns an interceptor which will observe N paths within `db`, and if any of them\n  test not identical? to their previous value  (as a result of a event handler\n  being run), then it will run `f` to compute a new value, which is then assoc-ed\n  into the given `out-path` within `db`.\n\n  Example Usage:\n\n      (defn my-f\n        [a-val b-val]\n        ... some computation on a and b in here)\n\n      ;; use it\n      (def my-interceptor (on-changes my-f [:c] [:a] [:b]))\n\n      (reg-event-db\n        :event-id\n        [... my-interceptor ...]  ;; <-- ultimately used here\n        (fn [db v]\n           ...))\n\n\n  If you put this Interceptor on handlers which might change paths `:a` or `:b`,\n  it will:\n\n    - call `f` each time the value at path `[:a]` or `[:b]` changes\n    - call `f` with the values extracted from `[:a]` `[:b]`\n    - assoc the return value from `f` into the path  `[:c]`\n  \"\n  [f out-path & in-paths]\n  (apply std-interceptors/on-changes (into [f out-path] in-paths)))\n\n\n(defn reg-global-interceptor\n  \"Registers the given `interceptor` as a global interceptor. Global interceptors are\n   included in the processing chain of every event.\n\n   When you register an event handler, you have the option of supplying an\n   interceptor chain. Any global interceptors you register are effectively\n   prepending to this chain.\n\n   Global interceptors are run in the order that they are registered.\"\n  [interceptor]\n  (settings/reg-global-interceptor interceptor))\n\n(defn clear-global-interceptor\n  \"Unregisters global interceptors (presumably registered previously via the use of `reg-global-interceptor`). \n   \n  When called with no args, it will unregister all currently registered global interceptors. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  global interceptors, it will unregister the associated interceptor. Will produce a warning to \n  console if it finds no matching registration.\"\n  ([]\n   (settings/clear-global-interceptors))\n  ([id]\n   (settings/clear-global-interceptors id)))\n\n\n(defn ->interceptor\n  \"A utility function for creating interceptors.\n\n  Accepts three optional, named arguments:\n\n     - `:id` - an id for the interceptor (decorative only)\n     - `:before` - the interceptor's before function\n     - `:after`  - the interceptor's after function\n\n  Example use:\n\n      (def my-interceptor\n        (->interceptor\n         :id     :my-interceptor\n         :before (fn [context]\n                   ... modifies and returns `context`)\n         :after  (fn [context] \n                   ... modifies and returns `context`)))\n   \n  Notes:\n  \n    - `:before` functions modify and return their `context` argument. Sometimes they \n      only side effect, in which case, they'll perform the side effect and return\n      `context` unchanged.\n    - `:before` functions often modify the `:coeffects` map within `context` and, \n      if they do, then they should use the utility functions `get-coeffect` and \n      `assoc-coeffect`.\n    - `:after` functions modify and return their `context` argument. Sometimes they \n      only side effect, in which case, they'll perform the side effect and return \n      `context` unchanged.\n    - `:after` functions often modify the `:effects` map within `context` and, \n      if they do, then they should use the utility functions `get-effect`\n      and `assoc-effect`\"\n  [& {:as m :keys [id before after]}]\n  (utils/apply-kw interceptor/->interceptor m))\n\n(defn get-coeffect\n  \"A utility function, typically used when writing an interceptor's `:before` function.\n\n   When called with one argument, it returns the `:coeffects` map from with that `context`.\n\n   When called with two or three arguments, behaves like `clojure.core/get` and\n   returns the value mapped to `key` in the `:coeffects` map within `context`, `not-found` or\n   `nil` if `key` is not present.\"\n  ([context]\n   (interceptor/get-coeffect context))\n  ([context key]\n   (interceptor/get-coeffect context key))\n  ([context key not-found]\n   (interceptor/get-coeffect context key not-found)))\n\n(defn assoc-coeffect\n  \"A utility function, typically used when writing an interceptor's `:before` function.\n\n   Adds or updates a key/value pair in the `:coeffects` map within `context`. \"\n  [context key value]\n  (interceptor/assoc-coeffect context key value))\n\n(defn get-effect\n  \"A utility function, used when writing interceptors, typically within an `:after` function.\n\n   When called with one argument, returns the `:effects` map from the `context`.\n\n   When called with two or three arguments, behaves like `clojure.core/get` and\n   returns the value mapped to `key` in the effects map, `not-found` or\n   `nil` if `key` is not present.\"\n  ([context]\n   (interceptor/get-effect context))\n  ([context key]\n   (interceptor/get-effect context key))\n  ([context key not-found]\n   (interceptor/get-effect context key not-found)))\n\n(defn assoc-effect\n   \"A utility function, typically used when writing an interceptor's `:after` function.\n\n   Adds or updates a key/value pair in the `:effects` map within `context`. \"\n  [context key value]\n  (interceptor/assoc-effect context key value))\n\n(defn enqueue\n  \"A utility function, used when writing an interceptor's `:before` function.\n\n  Adds the given collection of `interceptors` to those already in `context's` \n  execution `:queue`. It returns the updated `context`.\n   \n  So, it provides a way for one Interceptor to add more interceptors to the \n  currently executing interceptor chain.\n  \"\n  [context interceptors]\n  (interceptor/enqueue context interceptors))\n\n\n;; --  logging ----------------------------------------------------------------\n\n(defn set-loggers!\n  \"re-frame outputs warnings and errors via the API function `console` \n   which, by default, delegates to `js/console`'s default implementation for \n  `log`, `error`, `warn`, `debug`, `group` and `groupEnd`. But, using this function,\n   you can override that behaviour with your own functions. \n\n  The argument `new-loggers` should be a map containing a subset of they keys \n  for the standard `loggers`, namely  `:log` `:error` `:warn` `:debug` `:group` \n  or `:groupEnd`.\n\n  Example Usage:\n\n      (defn my-logger      ;; my alternative logging function\n        [& args]\n        (post-it-somewhere (apply str args)))\n\n      ;; now install my alternative loggers\n      (re-frame.core/set-loggers!  {:warn my-logger :log my-logger})\n   \"\n  [new-loggers]\n  (loggers/set-loggers! new-loggers))\n\n\n(defn console\n  \"A utility logging function which is used internally within re-frame to produce \n  warnings and other output. It can also be used by libraries which \n  extend re-frame, such as effect handlers.\n\n  By default, it will output the given `args` to `js/console` at the given log `level`.\n  However, an application using re-frame can redirect `console` output via `set-loggers!`. \n\n  `level` can be one of `:log`, `:error`, `:warn`, `:debug`, `:group` or `:groupEnd`.\n\n  Example usage:\n\n      (console :error \\\"Sure enough it happened:\\\" a-var \\\"and\\\" another)\n      (console :warn \\\"Possible breach of containment wall at:\\\" dt)\n  \"\n  [level & args]\n  (apply loggers/console (into [level] args)))\n\n;; -- unit testing ------------------------------------------------------------\n\n(defn make-restore-fn\n  \"This is a utility function, typically used in testing.\n\n  It checkpoints the current state of re-frame and returns a function which, when\n  later called, will restore re-frame to the checkpointed state.\n\n  The checkpoint includes `app-db`, all registered handlers and all subscriptions.\n  \"\n  []\n  (let [handlers @registrar/kind->id->handler\n        app-db   @db/app-db\n        subs-cache @subs/query->reaction]\n    (fn []\n      ;; call `dispose!` on all current subscriptions which\n      ;; didn't originally exist.\n      (let [original-subs (set (vals subs-cache))\n            current-subs  (set (vals @subs/query->reaction))]\n        (doseq [sub (set/difference current-subs original-subs)]\n          (interop/dispose! sub)))\n\n      ;; Reset the atoms\n      ;; We don't need to reset subs/query->reaction, as\n      ;; disposing of the subs removes them from the cache anyway\n      (reset! registrar/kind->id->handler handlers)\n      (reset! db/app-db app-db)\n      nil)))\n\n(defn purge-event-queue\n  \"Removes all events currently queued for processing\"\n  []\n  (router/purge re-frame.router/event-queue))\n\n\n;; -- Event Processing Callbacks  ---------------------------------------------\n\n(defn add-post-event-callback\n  \"Registers the given function `f` to be called after each event is processed. \n   \n   `f` will be called with two arguments:\n\n    - `event`: a vector. The event just processed.\n    - `queue`: a PersistentQueue, possibly empty, of events yet to be processed.\n\n   This facility is useful in advanced cases like:\n\n     - you are implementing a complex bootstrap pipeline\n     - you want to create your own handling infrastructure, with perhaps multiple\n       handlers for the one event, etc.  Hook in here.\n     - libraries providing 'isomorphic javascript' rendering on  Nodejs or Nashorn.\n\n  `id` is typically a keyword. If it supplied when an `f` is added, it can be \n  subsequently be used to identify it for removal. See `remove-post-event-callback`.\n  \"\n  ([f]\n   (add-post-event-callback f f))   ;; use f as its own identifier\n  ([id f]\n   (router/add-post-event-callback re-frame.router/event-queue id f)))\n\n\n(defn remove-post-event-callback\n  \"Unregisters a post event callback function, identified by `id`. \n   \n  Such a function must have been previously registered via `add-post-event-callback`\"\n  [id]\n  (router/remove-post-event-callback re-frame.router/event-queue id))\n\n\n;; --  Deprecation ------------------------------------------------------------\n;; Assisting the v0.7.x ->  v0.8.x transition.\n(defn register-handler\n  \"Deprecated. Use `reg-event-db` instead.\"\n  {:deprecated \"0.8.0\"}\n  [& args]\n  (console :warn  \"re-frame: \\\"register-handler\\\" has been renamed \\\"reg-event-db\\\" (look for registration of \" (str (first args)) \")\")\n  (apply reg-event-db args))\n\n(defn register-sub\n  \"Deprecated. Use `reg-sub-raw` instead.\"\n  {:deprecated \"0.8.0\"}\n  [& args]\n  (console :warn  \"re-frame: \\\"register-sub\\\" is used to register the event \" (str (first args)) \" but it is a deprecated part of the API. Please use \\\"reg-sub-raw\\\" instead.\")\n  (apply reg-sub-raw args))\n","~:reader-features",["^F",["~:cljs"]],"~:cljc",true,"~:source-map-compact",["^ ","mappings",";AAsBA;;;;;;;;;;;;;;;;AAAA,AAAMA,AAeHC;AAfH,AAgBE,AAACC,AAAgBD;;AAEnB;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAME,AAuBHF;AAvBH,AAwBE,AAACG,AAAqBH;;AAIxB,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAAI,AAAMM;AAAN,AAAA,AAAAL,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAAK,AAAA,AAAA,AAAA,AAAAF;;;AAAA,AAAA,AAAA,AAAA,AAAME,AA2IHM,AAAWC;AA3Id,AA4IE,AAACC,AAAMC,AAAa,AAAA,AAACC,AAAMJ,AAAUC;;;AA5IvC,AAAA,AAAA,AAAMP;;AAAN;AAAA,AAAA,AAAA,AAAAC,AAAMD;AAAN,AAAA,AAAAE,AAAA,AAAAC,AAAAF;AAAAA,AAAA,AAAAG,AAAAH;AAAA,AAAA,AAAAI,AAAA;AAAA,AAAA,AAAAA,AAAAH,AAAAD;;;AAAA,AA8IA,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAAP,AAAMkB;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMD,AAqDFE;AArDJ,AAsDG,AAACC,AAAeD;;;AAtDnB,AAAA,AAAA,AAAMF,AAuDFE,AAAME;AAvDV,AAwDG,AAACD,AAAeD,AAAME;;;AAxDzB,AAAA,AAAA,AAAMJ;;AAAN,AA0DA,AAAA;;;;;;;;;;;AAAA,AAAAlB,AAAMwB;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAL,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMK;AAAN,AAWG,AAACC,AAAyBC;;;AAX7B,AAAA,AAAA,AAAMF,AAYFZ;AAZJ,AAaG,AAACa,AAAyBC,AAAUd;;;AAbvC,AAAA,AAAA,AAAMY;;AAAN,AAgBA;;;;;;;;;;AAAA,AAAMG;AAAN,AAUE,AAACC;;AAEH;;;;;;;AAAA,AAAMC,AAMHjB,AAASkB;AANZ,AAOE,AAACC,AAA2BL,AAAUd,AAASkB;;AAIjD;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAME,AAqBHC,AAAGC;AArBN,AAsBE,AAACC,AAAUF,AAAGC;;AAGhB,AAAA;;;;;;;;;;AAAA,AAAAlC,AAAMqC;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAlB,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMkB;AAAN,AAUG,AAACZ,AAAyBa;;;AAV7B,AAAA,AAAA,AAAMD,AAWFJ;AAXJ,AAYG,AAACR,AAAyBa,AAAQL;;;AAZrC,AAAA,AAAA,AAAMI;;AAAN,AAeA;;;;;;;;;;;AAAA,AAAME,AAUHN,AAAGC;AAVN,AAWE,AAACM,AAAcP,AAAGC;;AAEpB,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAAlC,AAAM0C;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAvB,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMuB,AAwDFT;AAxDJ,AAyDG,AAACU,AAAiBV;;;AAzDrB,AAAA,AAAA,AAAMS,AA0DFT,AAAGW;AA1DP,AA2DG,AAACD,AAAiBV,AAAGW;;;AA3DxB,AAAA,AAAA,AAAMF;;AAAN,AA6DA,AAAA;;;;;;;;;AAAA,AAAA1C,AAAM8C;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAA3B,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAM2B;AAAN,AASG,AAACrB,AAAyBsB;;;AAT7B,AAAA,AAAA,AAAMD,AAUFb;AAVJ,AAWG,AAACR,AAAyBsB,AAAUd;;;AAXvC,AAAA,AAAA,AAAMa;;AAAN,AAeA,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAA9C,AAAMiD;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAA9B,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAM8B,AAyBFhB,AAAGC;AAzBP,AA0BG,AAAA,AAACgB,AAAajB,AAAOC;;;AA1BxB,AAAA,AAAA,AAAMe,AA2BFhB,AAAGkB,AAAajB;AA3BpB,AA4BG,AAAA,AAACkB,AAAgBnB,AAAIoB,AAAeC,AAASC,AAA4CJ,AAAa,AAACK,AAAwBtB;;;AA5BlI,AAAA,AAAA,AAAMe;;AAAN,AA+BA,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAAjD,AAAM0D;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAvC,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMuC,AA0BFzB,AAAGC;AA1BP,AA2BG,AAAA,AAACyB,AAAa1B,AAAOC;;;AA3BxB,AAAA,AAAA,AAAMwB,AA4BFzB,AAAGkB,AAAajB;AA5BpB,AA6BG,AAAA,AAACkB,AAAgBnB,AAAIoB,AAAeC,AAASC,AAA4CJ,AAAa,AAACS,AAAwB1B;;;AA7BlI,AAAA,AAAA,AAAMwB;;AAAN,AAgCA,AAAA;;;;;;;;;;AAAA,AAAA1D,AAAM8D;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAA3C,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAM2C,AASF7B,AAAGC;AATP,AAUG,AAAA,AAAC6B,AAAc9B,AAAOC;;;AAVzB,AAAA,AAAA,AAAM4B,AAWF7B,AAAGkB,AAAajB;AAXpB,AAYG,AAAA,AAACkB,AAAgBnB,AAAIoB,AAAeC,AAASC,AAA4CJ,AAAa,AAACa,AAAyB9B;;;AAZnI,AAAA,AAAA,AAAM4B;;AAAN,AAcA,AAAA;;;;;;;;;AAAA,AAAA9D,AAAMkE;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAA/C,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAM+C;AAAN,AASG,AAACzC,AAAyB0C;;;AAT7B,AAAA,AAAA,AAAMD,AAUFjC;AAVJ,AAWG,AAACR,AAAyB0C,AAAYlC;;;AAXzC,AAAA,AAAA,AAAMiC;;AAAN,AAeA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAKE,AA4BHC;AAEF,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAArE,AAAMsE;AAAN,AAAA,AAAArE,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAAqE,AAAAlE;;;AAAA,AAAA,AAAA,AAAA,AAAMkE,AA4BDzD;AA5BL,AA6BE,AAACC,AAAM4D,AAAsB7D;;;AA7B/B,AAAA,AAAA,AAAMyD;;AAAN;AAAA,AAAA,AAAA,AAAAC,AAAMD;AAAN,AAAA,AAAAE,AAAA;AAAA,AAAA,AAAAA,AAAA,AAAAC,AAAAF;;;AAAA,AA+BA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAMI,AA6CHC;AA7CH,AA8CE,AAACC,AAAwBD;;AAE3B;;;;;;;;;;;;;;AAAKE,AAaHC;AAEF;;;;;;;;;;;;;AAAA,AAAMC,AAYHJ;AAZH,AAaE,AAACK,AAAuBL;;AAE1B,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAA5E,AAAMkF;AAAN,AAAA,AAAAjF,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAAiF,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA9E;;;AAAA,AAAA,AAAA,AAAA,AAAM8E,AA6BHN,AAAEU,AAAWC;AA7BhB,AA8BE,AAACzE,AAAM0E,AAA4B,AAAA,AAACxE,AAAM4D,AAAEU,AAAUC;;;AA9BxD,AAAA,AAAA,AAAML;;AAAN;AAAA,AAAA,AAAA,AAAAC,AAAMD;AAAN,AAAA,AAAAE,AAAA,AAAA3E,AAAA0E;AAAAA,AAAA,AAAAzE,AAAAyE;AAAAE,AAAA,AAAA5E,AAAA0E;AAAAA,AAAA,AAAAzE,AAAAyE;AAAA,AAAA,AAAAxE,AAAA;AAAA,AAAA,AAAAA,AAAAyE,AAAAC,AAAAF;;;AAAA,AAiCA;;;;;;;;;;AAAA,AAAMM,AASHC;AATH,AAUE,AAACC,AAAgCD;;AAEnC,AAAA;;;;;;;;;AAAA,AAAA1F,AAAM6F;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAA1E,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAM0E;AAAN,AASG,AAACC;;;AATJ,AAAA,AAAA,AAAMD,AAUF5D;AAVJ,AAWG,AAAC6D,AAAmC7D;;;AAXvC,AAAA,AAAA,AAAM4D;;AAAN,AAcA,AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA,AAAA7F,AAAM+F;AAAN,AAAA,AAAA9F,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAA8F,AAAA3F;;;AAAA,AAAA,AAAA,AAAA,AAAA4F,AAAMD;AAAN,AAAA,AAAAE,AAAAD;AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAAA,AAAA,AAAA,AAAAC,AAAA,AAAAD,AAAA,AAAA,AAAA,AAAA,AAAAnF,AAAAqF,AAAAF,AAAAA;AAAAA,AAiCUK;AAjCV,AAAAF,AAAAH,AAAA,AAiCmBhE;AAjCnB,AAAAmE,AAAAH,AAAA,AAiCsBM;AAjCtB,AAAAH,AAAAH,AAAA,AAiC6BO;AAjC7B,AAkCE,AAACC,AAAeC,AAA0BJ;;;AAlC5C,AAAA,AAAA,AAAMP;;AAAN;AAAA,AAAA,AAAA,AAAAM,AAAMN;AAAN,AAAA,AAAAvB,AAAA;AAAA,AAAA,AAAAA,AAAA,AAAAC,AAAA4B;;;AAAA,AAoCA,AAAA;;;;;;;;;AAAA,AAAArG,AAAM4G;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAzF,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMyF,AAQFC;AARJ,AASG,AAACC,AAAyBD;;;AAT7B,AAAA,AAAA,AAAMD,AAUFC,AAAQE;AAVZ,AAWG,AAACD,AAAyBD,AAAQE;;;AAXrC,AAAA,AAAA,AAAMH,AAYFC,AAAQE,AAAIC;AAZhB,AAaG,AAACF,AAAyBD,AAAQE,AAAIC;;;AAbzC,AAAA,AAAA,AAAMJ;;AAAN,AAeA;;;;;AAAA,AAAMK,AAIHJ,AAAQE,AAAInE;AAJf,AAKE,AAACsE,AAA2BL,AAAQE,AAAInE;;AAE1C,AAAA;;;;;;;;;AAAA,AAAA5C,AAAMoH;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAAjG,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAMiG,AAQFP;AARJ,AASG,AAACQ,AAAuBR;;;AAT3B,AAAA,AAAA,AAAMO,AAUFP,AAAQE;AAVZ,AAWG,AAACM,AAAuBR,AAAQE;;;AAXnC,AAAA,AAAA,AAAMK,AAYFP,AAAQE,AAAIC;AAZhB,AAaG,AAACK,AAAuBR,AAAQE,AAAIC;;;AAbvC,AAAA,AAAA,AAAMI;;AAAN,AAeA;;;;;AAAA,AAAME,AAIHT,AAAQE,AAAInE;AAJf,AAKE,AAAC2E,AAAyBV,AAAQE,AAAInE;;AAExC;;;;;;;;;;AAAA,AAAM4E,AASHX,AAAQ1D;AATX,AAUE,AAACsE,AAAoBZ,AAAQ1D;;AAK/B;;;;;;;;;;;;;;;;;;;;AAAA,AAAMuE,AAmBHC;AAnBH,AAoBE,AAACC,AAAqBD;;AAGxB,AAAA;;;;;;;;;;;;;;;;AAAA,AAAA3H,AAAM6H;AAAN,AAAA,AAAA5H,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAA4H,AAAA,AAAA,AAAA,AAAAzH;;;AAAA,AAAA,AAAA,AAAA,AAAMyH,AAeHG,AAAQnH;AAfX,AAgBE,AAACC,AAAMmH,AAAgB,AAAA,AAACjH,AAAMgH,AAAOnH;;;AAhBvC,AAAA,AAAA,AAAMgH;;AAAN;AAAA,AAAA,AAAA,AAAAC,AAAMD;AAAN,AAAA,AAAAE,AAAA,AAAAtH,AAAAqH;AAAAA,AAAA,AAAApH,AAAAoH;AAAA,AAAA,AAAAnH,AAAA;AAAA,AAAA,AAAAA,AAAAoH,AAAAD;;;AAAA,AAoBA;;;;;;;;;AAAA,AAAMI;AAAN,AASE,AAAA,AAAAC,AAAMC,AAAUC;AAAhB,AAAAF,AACMG,AAAUC;AADhB,AAAAJ,AAEMK,AAAYC;AAFlB,AAGE;AAAA,AAGE,AAAMC,AAAc,AAACC,AAAI,AAACC,AAAKJ;AACzBK,AAAc,AAACF,AAAI,AAAA,AAAAR,AAACS,AAAMH;AADhC,AAEE,AAAAK,AAAA,AAAArE,AAAY,AAACgF,AAAeZ,AAAaH;AAAzCK,AAAA;AAAAC,AAAA;AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAAE,AAAQO;AAAR,AAAA,AACE,AAACE,AAAiBF;;AADpB;AAAA,AAAAV;AAAAC;AAAAC;AAAA,AAAAC,AAAA;;;;;;;AAAA,AAAAC,AAAA,AAAAzE,AAAAqE;AAAA,AAAA,AAAAI;AAAA,AAAA,AAAAJ,AAAAI;AAAA,AAAA,AAAA,AAAAC,AAAAL;AAAA,AAAAM,AAAA,AAAAC,AAAAP;AAAA,AAAA,AAAA,AAAAQ,AAAAR;AAAAM;AAAA,AAAAG,AAAAH;AAAA;;;;;;;AAAA,AAAA,AAAA3I,AAAAqI,AAAQU;AAAR,AAAA,AACE,AAACE,AAAiBF;;AADpB;AAAA,AAAA,AAAA9I,AAAAoI;AAAA;AAAA;AAAA;;;;;;;;AAAA;;;;;AAMF,AAACa,AAAOtB,AAA4BD;;AACpC,AAACuB,AAAOpB,AAAUD;;AAZpB;;;AAeJ;;;AAAA,AAAMsB;AAAN,AAGE,AAAcC;;AAKhB,AAAA;;;;;;;;;;;;;;;;;;;AAAA,AAAA7J,AAAM+J;AAAN,AAAA,AAAAD,AAAA,AAAA;AAAA,AAAA,AAAAA;AAAA;AAAA,AAAAC,AAAA,AAAA,AAAA;;;AAAA;AAAA,AAAAA,AAAA,AAAA,AAAA,AAAA,AAAA,AAAA;;;;AAAA,AAAA,AAAA5I,AAAA,AAAA,AAAA,AAAA;;;;;AAAA,AAAA,AAAA,AAAM4I,AAkBFnF;AAlBJ,AAmBG,AAACoF,AAAwBpF,AAAEA;;;AAnB9B,AAAA,AAAA,AAAMmF,AAoBF9H,AAAG2C;AApBP,AAqBG,AAAgCiF,AAA4B5H,AAAG2C;;;AArBlE,AAAA,AAAA,AAAMmF;;AAAN,AAwBA;;;;;AAAA,AAAME,AAIHhI;AAJH,AAKE,AAAmC4H,AAA4B5H;;AAKjE,AAAA;;;AAAA,AAAAjC,AAAMkK;AAAN,AAAA,AAAAjK,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAAiK,AAAA9J;;;AAAA,AAAA,AAAA,AAAA,AAAM8J,AAGDrJ;AAHL,AAIE,AAAA,AAAA,AAAA,AAACuJ,AAA6G,AAAK,AAAC3J,AAAMI;;AAC1H,AAACC,AAAMmC,AAAapC;;;AALtB,AAAA,AAAA,AAAMqJ;;AAAN;AAAA,AAAA,AAAA,AAAAC,AAAMD;AAAN,AAAA,AAAA1F,AAAA;AAAA,AAAA,AAAAA,AAAA,AAAAC,AAAA0F;;;AAAA,AAOA,AAAA;;;AAAA,AAAAnK,AAAMqK;AAAN,AAAA,AAAApK,AAAA;AAAA,AAAA,AAAAC,AAAA,AAAA;AAAA,AAAA,AAAAC,AAAA;;AAAA,AAAA,AAAA,AAAAA,AAAAD;AAAA,AAAA,AAAAD,AAAA,AAAA,AAAAE;;AAAA,AAAA,AAAAA,AAAA;;;;AAAA;;;;AAAA,AAAAC,AAAA,AAAA,AAAA,AAAA,AAAAH,AAAA,AAAA,AAAAI,AAAA,AAAAJ,AAAA,AAAA,AAAA,AAAA;AAAA,AAAA,AAAAoK,AAAAjK;;;AAAA,AAAA,AAAA,AAAA,AAAMiK,AAGDxJ;AAHL,AAIE,AAAA,AAAA,AAAA,AAACuJ,AAA2E,AAAK,AAAC3J,AAAMI;;AACxF,AAACC,AAAMe,AAAYhB;;;AALrB,AAAA,AAAA,AAAMwJ;;AAAN;AAAA,AAAA,AAAA,AAAAC,AAAMD;AAAN,AAAA,AAAA7F,AAAA;AAAA,AAAA,AAAAA,AAAA,AAAAC,AAAA6F;;;AAAA","names",["re-frame.core/dispatch","event","re-frame.router/dispatch","re-frame.core/dispatch-sync","re-frame.router/dispatch-sync","var_args","args__4742__auto__","len__4736__auto__","i__4737__auto__","argseq__4743__auto__","cljs.core/IndexedSeq","re-frame.core/reg-sub","seq49163","G__49164","cljs.core/first","cljs.core/next","self__4723__auto__","query-id","args","cljs.core.apply","re-frame.subs/reg-sub","cljs.core.into","G__49179","re-frame.core/subscribe","js/Error","query","re_frame.subs.subscribe","dynv","G__49195","re-frame.core/clear-sub","re_frame.registrar.clear_handlers","re-frame.subs/kind","re-frame.core/clear-subscription-cache!","re-frame.subs/clear-subscription-cache!","re-frame.core/reg-sub-raw","handler-fn","re-frame.registrar/register-handler","re-frame.core/reg-fx","id","handler","re-frame.fx/reg-fx","G__49219","re-frame.core/clear-fx","re-frame.fx/kind","re-frame.core/reg-cofx","re-frame.cofx/reg-cofx","G__49237","re-frame.core/inject-cofx","re_frame.cofx.inject_cofx","value","G__49249","re-frame.core/clear-cofx","re-frame.cofx/kind","G__49272","re-frame.core/reg-event-db","re_frame.core.reg_event_db","interceptors","re-frame.events/register","re-frame.cofx/inject-db","re-frame.fx/do-fx","re-frame.std-interceptors/inject-global-interceptors","re-frame.std-interceptors/db-handler->interceptor","G__49285","re-frame.core/reg-event-fx","re_frame.core.reg_event_fx","re-frame.std-interceptors/fx-handler->interceptor","G__49288","re-frame.core/reg-event-ctx","re_frame.core.reg_event_ctx","re-frame.std-interceptors/ctx-handler->interceptor","G__49294","re-frame.core/clear-event","re-frame.events/kind","re-frame.core/debug","re-frame.std-interceptors/debug","re-frame.core/path","seq49298","self__4724__auto__","cljs.core/seq","re-frame.std-interceptors/path","re-frame.core/enrich","f","re-frame.std-interceptors/enrich","re-frame.core/trim-v","re-frame.std-interceptors/trim-v","re-frame.core/after","re-frame.std-interceptors/after","re-frame.core/on-changes","seq49315","G__49316","G__49317","out-path","in-paths","re-frame.std-interceptors/on-changes","re-frame.core/reg-global-interceptor","interceptor","re-frame.settings/reg-global-interceptor","G__49335","re-frame.core/clear-global-interceptor","re_frame.settings.clear_global_interceptors","re-frame.core/->interceptor","p__49340","map__49341","cljs.core/PROTOCOL_SENTINEL","cljs.core/hash-map","cljs.core.get","seq49338","m","before","after","re_frame.utils.apply_kw","re-frame.interceptor/->interceptor","G__49346","re-frame.core/get-coeffect","context","re_frame.interceptor.get_coeffect","key","not-found","re-frame.core/assoc-coeffect","re-frame.interceptor/assoc-coeffect","G__49362","re-frame.core/get-effect","re_frame.interceptor.get_effect","re-frame.core/assoc-effect","re-frame.interceptor/assoc-effect","re-frame.core/enqueue","re-frame.interceptor/enqueue","re-frame.core/set-loggers!","new-loggers","re-frame.loggers/set-loggers!","re-frame.core/console","seq49371","G__49372","level","re-frame.loggers/console","re-frame.core/make-restore-fn","cljs.core/deref","handlers","re-frame.registrar/kind->id->handler","app-db","re-frame.db/app-db","subs-cache","re-frame.subs/query->reaction","original-subs","cljs.core/set","cljs.core/vals","current-subs","seq__49381","chunk__49382","count__49383","i__49384","temp__5735__auto__","cljs.core/chunked-seq?","c__4556__auto__","cljs.core/chunk-first","cljs.core/chunk-rest","cljs.core/count","sub","clojure.set.difference","re-frame.interop/dispose!","cljs.core/reset!","re-frame.core/purge-event-queue","re-frame.router/event-queue","G__49399","re-frame.core/add-post-event-callback","re_frame.core.add_post_event_callback","re-frame.core/remove-post-event-callback","re-frame.core/register-handler","seq49412","re_frame.core.console","re-frame.core/register-sub","seq49427"]],"~:used-vars",["^F",["~$re-frame.router/purge","~$re-frame.core/add-post-event-callback","~$re-frame.core/remove-post-event-callback","~$re-frame.interceptor/get-effect","~$re-frame.fx/kind","~$re-frame.core/clear-sub","~$re-frame.fx/reg-fx","~$re-frame.db/app-db","~$re-frame.core/clear-event","~$re-frame.core/register-sub","~$re-frame.core/assoc-coeffect","~$re-frame.fx/do-fx","~$re-frame.interop/dispose!","~$re-frame.loggers/set-loggers!","~$re-frame.std-interceptors/debug","~$re-frame.core/dispatch","~$re-frame.interceptor/->interceptor","~$re-frame.core/on-changes","~$cljs.core/count","~$re-frame.events/register","~$cljs.core/seq","~$re-frame.settings/reg-global-interceptor","~$cljs.core/apply","~$re-frame.events/kind","~$re-frame.core/enrich","~$re-frame.registrar/clear-handlers","~$re-frame.loggers/console","~$re-frame.core/get-coeffect","~$re-frame.std-interceptors/inject-global-interceptors","~$re-frame.core/assoc-effect","~$cljs.core/chunk-rest","~$re-frame.std-interceptors/trim-v","~$re-frame.core/reg-event-db","~$re-frame.core/reg-sub-raw","~$re-frame.core/dispatch-sync","~$re-frame.interceptor/enqueue","~$re-frame.core/subscribe","~$re-frame.std-interceptors/db-handler->interceptor","~$re-frame.core/trim-v","~$cljs.core/into","~$cljs.core/reset!","~$re-frame.registrar/register-handler","~$re-frame.subs/clear-subscription-cache!","~$re-frame.subs/kind","~$re-frame.core/reg-fx","~$re-frame.core/purge-event-queue","~$re-frame.core/get-effect","~$re-frame.std-interceptors/enrich","~$re-frame.subs/subscribe","~$re-frame.core/clear-cofx","~$re-frame.core/reg-event-ctx","~$re-frame.std-interceptors/ctx-handler->interceptor","~$re-frame.core/reg-event-fx","~$re-frame.interceptor/assoc-coeffect","~$re-frame.core/clear-fx","~$re-frame.cofx/reg-cofx","~$re-frame.cofx/inject-cofx","~$re-frame.std-interceptors/fx-handler->interceptor","~$re-frame.subs/reg-sub","~$re-frame.cofx/kind","~$re-frame.core/register-handler","~$re-frame.router/dispatch-sync","~$re-frame.std-interceptors/after","~$re-frame.router/add-post-event-callback","~$re-frame.core/->interceptor","~$re-frame.core/inject-cofx","~$cljs.core/next","~$re-frame.core/set-loggers!","~$re-frame.interceptor/get-coeffect","~$re-frame.core/make-restore-fn","~$re-frame.interceptor/assoc-effect","~$re-frame.core/clear-subscription-cache!","~$re-frame.core/reg-sub","~$re-frame.utils/apply-kw","~$re-frame.cofx/inject-db","~$re-frame.router/event-queue","~$re-frame.std-interceptors/path","~$re-frame.core/clear-global-interceptor","~$re-frame.core/console","~$re-frame.router/remove-post-event-callback","~$re-frame.core/reg-global-interceptor","~$re-frame.core/reg-cofx","~$re-frame.router/dispatch","~$cljs.core/first","~$re-frame.core/path","~$re-frame.core/enqueue","~$re-frame.core/debug","~$js/Error","~$re-frame.std-interceptors/on-changes","~$re-frame.registrar/kind->id->handler","~$re-frame.settings/clear-global-interceptors","~$cljs.core/chunked-seq?","~$re-frame.core/after"]]],"~:cache-keys",["~#cmap",[["^1O","reagent/impl/batching.cljs"],["71172e9be671755156730f86af647b7c667093fa","~:shadow.build.compiler/resolve",["^ ","~:require-id",null,"~:deps-ids",["^F",[]],"~:deps-syms",["^12","^10","~$reagent.debug","~$reagent.impl.util"]]],["^1O","goog/dom/tagname.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.dom.HtmlElement"]]],["^1O","goog/labs/useragent/platform.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.labs.userAgent.util","~$goog.string"]]],["^1O","goog/math/math.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.array","~$goog.asserts"]]],["^1O","goog/html/trustedtypes.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/events/eventtype.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.events.BrowserFeature","~$goog.userAgent"]]],["^1O","goog/labs/useragent/browser.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4=","~$goog.object","~$goog.string.internal"]]],["^1O","goog/html/safeurl.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","~$goog.fs.url","~$goog.html.TrustedResourceUrl","~$goog.i18n.bidi.Dir","~$goog.i18n.bidi.DirectionalString","~$goog.string.Const","~$goog.string.TypedString","^4D"]]],["^1O","re_frame/loggers.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^Q"]]],["^1O","goog/array/array.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@"]]],["^1O","reagent/impl/util.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","~$clojure.string","~$clojure.walk","^4C","^4:"]]],["^1O","goog/useragent/useragent.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.labs.userAgent.browser","~$goog.labs.userAgent.engine","~$goog.labs.userAgent.platform","^4=","~$goog.reflect","^4>"]]],["^1O","re_frame/router.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^W","^M","^Y","~$re-frame.trace"]]],["^1O","goog/debug/error.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/events/events.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","~$goog.debug.entryPointRegistry","~$goog.events.BrowserEvent","^4A","~$goog.events.Listenable","~$goog.events.ListenerMap"]]],["^1O","re_frame/registrar.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^M","^Y","^Z"]]],["^1O","goog/events/browserfeature.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4B"]]],["^1O","goog/dom/nodetype.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","reagent/ratom.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^4;","^4:","~$reagent.impl.batching","^Q","^4C"]]],["^1O","re_frame/interop.cljs"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","~$goog.async.nextTick","~$goog.events","~$reagent.core","~$reagent.ratom"]]],["^1O","goog/disposable/disposable.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.disposable.IDisposable"]]],["^1O","goog/string/typedstring.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/object/object.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","reagent/impl/template.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^A","^4K","^4;","~$reagent.impl.component","^4V","~$reagent.impl.input","~$reagent.impl.protocols","^4Z","^4:","^4C"]]],["^1O","goog/dom/asserts.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@"]]],"~:SHADOW-TIMESTAMP",[1598798247000,1598798247000,1592608845000],["^1O","re_frame/events.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^16","^18","^M","^[","^Y","^T","^4Q"]]],["^1O","goog/math/long.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","^4P"]]],["^1O","goog/events/listener.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.events.ListenableKey"]]],["^1O","goog/html/trustedresourceurl.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","~$goog.html.trustedtypes","^4G","^4H","^4I","^4J"]]],["^1O","goog/events/listenermap.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","~$goog.events.Listener","^4C"]]],["^1O","goog/events/eventid.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/string/internal.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/functions/functions.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/html/safestyle.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","~$goog.html.SafeUrl","^4I","^4J","^4D"]]],["^1O","goog/dom/safe.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","~$goog.dom.asserts","~$goog.functions","~$goog.html.SafeHtml","~$goog.html.SafeScript","~$goog.html.SafeStyle","^57","^4F","~$goog.html.uncheckedconversions","^4I","^4D"]]],["^1O","reagent/impl/component.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^4C","^A","^4;","^4V","^52","^4Z","^4:"]]],["^1O","clojure/walk.cljs"],["9f9729dbbf9b814c83dc189977b447d2ae92b6cd","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10"]]],["^1O","goog/structs/map.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.iter.Iterator","~$goog.iter.StopIteration"]]],["^1O","goog/html/safehtml.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","~$goog.dom.TagName","~$goog.dom.tags","^5;","^5<","~$goog.html.SafeStyleSheet","^57","^4F","^55","^4G","^4H","^4M","^4C","^4I","^4J","^4D"]]],["^1O","goog/dom/tags.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4C"]]],["^1O","goog/math/size.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/labs/useragent/engine.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4=","^4>"]]],["^1O","re_frame/settings.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^M","^Y"]]],["^1O","goog/dom/dom.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","~$goog.dom.BrowserFeature","~$goog.dom.NodeType","^5@","~$goog.dom.safe","^5:","^5=","~$goog.math.Coordinate","~$goog.math.Size","^4C","^4>","~$goog.string.Unicode","^4B"]]],["^1O","goog/asserts/asserts.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.debug.Error","^5D"]]],["^1O","reagent/impl/protocols.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10"]]],["^1O","goog/uri/uri.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","^4>","~$goog.structs","~$goog.structs.Map","~$goog.uri.utils","~$goog.uri.utils.ComponentIndex","~$goog.uri.utils.StandardQueryParam"]]],["^1O","goog/i18n/bidi.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","re_frame/db.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^M"]]],["^1O","goog/disposable/idisposable.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/fs/url.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/base.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",[]]],["^1O","goog/structs/structs.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4C"]]],["^1O","clojure/string.cljs"],["9f9729dbbf9b814c83dc189977b447d2ae92b6cd","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^4>","~$goog.string.StringBuffer"]]],["^1O","re_frame/cofx.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^16","^T","^[","^Y"]]],["~:shadow.build.js-support/require","react"],["^A","shadow.js.shim.module$react.js","require","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/debug/entrypointregistry.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@"]]],["^1O","goog/string/string.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^5E","^5=","^4I","^4D"]]],["^1O","re_frame/interceptor.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^Y","^M","^4Q","^Q"]]],["^1O","clojure/data.cljs"],["9f9729dbbf9b814c83dc189977b447d2ae92b6cd","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^Q"]]],["^1O","goog/reflect/reflect.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/labs/useragent/util.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4D"]]],["^1O","reagent/core.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^A","~$reagent.impl.template","^50","^4;","^4V","^52","^4Z","^4:"]]],["^1O","goog/debug/debug.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","~$goog.debug.errorcontext","^4B"]]],["^1O","goog/string/stringbuffer.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/math/coordinate.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.math"]]],["^1O","re_frame/std_interceptors.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^T","^Y","^Z","^16","~$clojure.data","^S","^18","^4Q"]]],["^1O","goog/debug/errorcontext.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","goog/iter/iter.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","^59","^5S"]]],["^1O","goog/async/nexttick.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4R","~$goog.dom","^5@","^5E","^59","^5:","^4F","^4M","^4N","^4I"]]],["^1O","goog/html/uncheckedconversions.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","^5:","^5;","^5<","^5B","^57","^4F","^4I","^4D"]]],["^1O","re_frame/utils.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^Y"]]],["^1O","re_frame/fx.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^14","^16","^T","^M","^W","^[","^Y","^4Q"]]],["^1O","reagent/impl/input.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^50","^4V","^52"]]],["^1O","goog/events/event.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.Disposable","~$goog.events.EventId"]]],["^1O","goog/dom/htmlelement.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12"]]],["^1O","cljs/core.cljs"],["9f9729dbbf9b814c83dc189977b447d2ae92b6cd","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.math.Long","~$goog.math.Integer","^4>","^4C","^4?","~$goog.Uri","^5O"]]],["^1O","goog/html/safescript.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","^55","^4I","^4J"]]],["^1O","reagent/debug.cljs"],["71172e9be671755156730f86af647b7c667093fa","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10"]]],["^1O","goog/html/safestylesheet.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","^5<","^4C","^4I","^4J","^4D"]]],["^1O","goog/events/browserevent.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","~$goog.debug","^4A","~$goog.events.Event","~$goog.events.EventType","^4P","^4B"]]],["^1O","goog/math/integer.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4P"]]],["^1O","goog/dom/browserfeature.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4B"]]],["^1O","clojure/set.cljs"],["9f9729dbbf9b814c83dc189977b447d2ae92b6cd","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10"]]],["^1O","goog/uri/utils.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4?","^4@","^4>"]]],["^1O","goog/string/const.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^4@","^4J"]]],["^1O","goog/events/listenable.js"],["6025affb7181cd40418600864f58eed1ea80055d","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^5W"]]],["^1O","re_frame/trace.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^M","^Y","^59"]]],["^1O","re_frame/subs.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^16","^M","^Y","^18","^[","^4Q"]]],["^1O","re_frame/core.cljc"],["0e1666916193eaabc7012c4a18450a0d00336095","^46",["^ ","^47",null,"^48",["^F",[]],"^49",["^12","^10","^W","^O","^M","^16","^V","^S","^14","^Z","^Y","^[","^T","^1;","^18","^Q"]]]]],"~:clj-info",["^ ","jar:file:/home/justin/.m2/repository/re-frame/re-frame/1.1.1/re-frame-1.1.1.jar!/re_frame/interop.clj",1599498230000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/env.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/analyzer.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/tools.reader/1.3.3/tools.reader-1.3.3.jar!/clojure/tools/reader/default_data_readers.clj",1598798245000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/string.clj",1592060007000,"jar:file:/home/justin/.m2/repository/org/clojure/tools.reader/1.3.3/tools.reader-1.3.3.jar!/clojure/tools/reader/impl/errors.clj",1598798245000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/pprint.clj",1592060007000,"jar:file:/home/justin/.m2/repository/reagent/reagent/1.0.0-alpha2/reagent-1.0.0-alpha2.jar!/reagent/core.clj",1592063583000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/externs.clj",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/core.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/instant.clj",1592060007000,"jar:file:/home/justin/.m2/repository/reagent/reagent/1.0.0-alpha2/reagent-1.0.0-alpha2.jar!/reagent/ratom.clj",1592063583000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/set.clj",1592060007000,"jar:file:/home/justin/.m2/repository/org/clojure/tools.reader/1.3.3/tools.reader-1.3.3.jar!/clojure/tools/reader/reader_types.clj",1598798245000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/edn.clj",1592060007000,"jar:file:/home/justin/.m2/repository/org/clojure/tools.reader/1.3.3/tools.reader-1.3.3.jar!/clojure/tools/reader.clj",1598798245000,"jar:file:/home/justin/.m2/repository/reagent/reagent/1.0.0-alpha2/reagent-1.0.0-alpha2.jar!/reagent/debug.clj",1592063583000,"jar:file:/home/justin/.m2/repository/org/clojure/tools.reader/1.3.3/tools.reader-1.3.3.jar!/clojure/tools/reader/impl/inspect.clj",1598798245000,"jar:file:/home/justin/.m2/repository/org/clojure/data.json/1.0.0/data.json-1.0.0.jar!/clojure/data/json.clj",1592063582000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/util.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/source_map/base64_vlq.clj",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/js_deps.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/java/io.clj",1592060007000,"jar:file:/home/justin/.m2/repository/net/cgrand/macrovich/0.2.1/macrovich-0.2.1.jar!/net/cgrand/macrovich.cljc",1592063583000,"jar:file:/home/justin/.m2/repository/re-frame/re-frame/1.1.1/re-frame-1.1.1.jar!/re_frame/trace.cljc",1599498230000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/compiler.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/reagent/reagent/1.0.0-alpha2/reagent-1.0.0-alpha2.jar!/reagent/interop.clj",1592063583000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/tagged_literals.cljc",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar!/clojure/core.clj",1592060007000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/source_map.clj",1592608845000,"jar:file:/home/justin/.m2/repository/org/clojure/clojurescript/1.10.773/clojurescript-1.10.773.jar!/cljs/source_map/base64.clj",1592608845000],"~:analyzer",["^ ","^3",null,"^4",["^ "],"^5",["^ ","^6","re_frame/core.cljc","^7",1,"^8",5,"^9",1,"^:",18],"^;",["^ ","^<","^=","^>","^?","^@","^A","^B","^C"],"^D",null,"^E",["^F",[]],"^G","^H","^K",null,"^L",["^ ","^M","^M","^N","^O","^P","^Q","^R","^S","^T","^T","^U","^V","^W","^W","^X","^Y","^Z","^Z","^V","^V","^[","^[","^10","^10","^11","^T","^12","^12","^13","^14","^15","^16","^17","^[","^14","^14","^18","^18","^Q","^Q","^19","^W","^1:","^Z","^1;","^1;","^Y","^Y","^O","^O","^1<","^M","^1=","^18","^1>","^1;","^S","^S","^16","^16"],"^1?",["^F",["^1@"]],"~:shadow/js-access-global",["^F",["Error"]],"^1A",["^ ","^1B","^1;","^1C","^1;","^1D","^1;"],"~:defs",["^ ","~$console",["^ ","~:protocol-inline",null,"^5",["^ ","^6","re_frame/core.cljc","^7",845,"^8",7,"^9",845,"^:",14,"~:arglists",["^1G",["~$quote",["^1G",[["~$level","~$&","~$args"]]]]],"~:doc","A utility logging function which is used internally within re-frame to produce \n  warnings and other output. It can also be used by libraries which \n  extend re-frame, such as effect handlers.\n\n  By default, it will output the given `args` to `js/console` at the given log `level`.\n  However, an application using re-frame can redirect `console` output via `set-loggers!`. \n\n  `level` can be one of `:log`, `:error`, `:warn`, `:debug`, `:group` or `:groupEnd`.\n\n  Example usage:\n\n      (console :error \"Sure enough it happened:\" a-var \"and\" another)\n      (console :warn \"Possible breach of containment wall at:\" dt)\n  ","~:top-fn",["^ ","~:variadic?",true,"~:fixed-arity",1,"~:max-fixed-arity",1,"~:method-params",[["^1G",["^6Y","^6Z"]]],"^6W",["^1G",[["^6Y","~$&","^6Z"]]],"~:arglists-meta",["^1G",[null]]]],"^G","^3Q","^6","re_frame/core.cljc","^:",14,"^70",["^ ","^71",true,"^72",1,"^73",1,"^74",[["^1G",["^6Y","^6Z"]]],"^6W",["^1G",[["^6Y","~$&","^6Z"]]],"^75",["^1G",[null]]],"^74",[["^1G",["^6Y","^6Z"]]],"~:protocol-impl",null,"^72",1,"^75",["^1G",[null]],"^8",1,"^71",true,"~:methods",[["^ ","^72",1,"^71",true,"~:tag","~$any"]],"^7",845,"~:ret-tag","^79","^9",845,"^73",1,"~:fn-var",true,"^6W",["^1G",[["^6Y","~$&","^6Z"]]],"^6[","A utility logging function which is used internally within re-frame to produce \n  warnings and other output. It can also be used by libraries which \n  extend re-frame, such as effect handlers.\n\n  By default, it will output the given `args` to `js/console` at the given log `level`.\n  However, an application using re-frame can redirect `console` output via `set-loggers!`. \n\n  `level` can be one of `:log`, `:error`, `:warn`, `:debug`, `:group` or `:groupEnd`.\n\n  Example usage:\n\n      (console :error \"Sure enough it happened:\" a-var \"and\" another)\n      (console :warn \"Possible breach of containment wall at:\" dt)\n  "],"~$on-changes",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",668,"^8",7,"^9",668,"^:",17,"^6W",["^1G",["^6X",["^1G",[["~$f","~$out-path","~$&","~$in-paths"]]]]],"^6[","Returns an interceptor which will observe N paths within `db`, and if any of them\n  test not identical? to their previous value  (as a result of a event handler\n  being run), then it will run `f` to compute a new value, which is then assoc-ed\n  into the given `out-path` within `db`.\n\n  Example Usage:\n\n      (defn my-f\n        [a-val b-val]\n        ... some computation on a and b in here)\n\n      ;; use it\n      (def my-interceptor (on-changes my-f [:c] [:a] [:b]))\n\n      (reg-event-db\n        :event-id\n        [... my-interceptor ...]  ;; <-- ultimately used here\n        (fn [db v]\n           ...))\n\n\n  If you put this Interceptor on handlers which might change paths `:a` or `:b`,\n  it will:\n\n    - call `f` each time the value at path `[:a]` or `[:b]` changes\n    - call `f` with the values extracted from `[:a]` `[:b]`\n    - assoc the return value from `f` into the path  `[:c]`\n  ","^70",["^ ","^71",true,"^72",2,"^73",2,"^74",[["^1G",["~$f","^7=","^7>"]]],"^6W",["^1G",[["~$f","^7=","~$&","^7>"]]],"^75",["^1G",[null]]]],"^G","^2@","^6","re_frame/core.cljc","^:",17,"^70",["^ ","^71",true,"^72",2,"^73",2,"^74",[["^1G",["~$f","^7=","^7>"]]],"^6W",["^1G",[["~$f","^7=","~$&","^7>"]]],"^75",["^1G",[null]]],"^74",[["^1G",["~$f","^7=","^7>"]]],"^76",null,"^72",2,"^75",["^1G",[null]],"^8",1,"^71",true,"^77",[["^ ","^72",2,"^71",true,"^78","^79"]],"^7",668,"^7:","^79","^9",668,"^73",2,"^7;",true,"^6W",["^1G",[["~$f","^7=","~$&","^7>"]]],"^6[","Returns an interceptor which will observe N paths within `db`, and if any of them\n  test not identical? to their previous value  (as a result of a event handler\n  being run), then it will run `f` to compute a new value, which is then assoc-ed\n  into the given `out-path` within `db`.\n\n  Example Usage:\n\n      (defn my-f\n        [a-val b-val]\n        ... some computation on a and b in here)\n\n      ;; use it\n      (def my-interceptor (on-changes my-f [:c] [:a] [:b]))\n\n      (reg-event-db\n        :event-id\n        [... my-interceptor ...]  ;; <-- ultimately used here\n        (fn [db v]\n           ...))\n\n\n  If you put this Interceptor on handlers which might change paths `:a` or `:b`,\n  it will:\n\n    - call `f` each time the value at path `[:a]` or `[:b]` changes\n    - call `f` with the values extracted from `[:a]` `[:b]`\n    - assoc the return value from `f` into the path  `[:c]`\n  "],"~$enrich",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",590,"^8",7,"^9",590,"^:",13,"^6W",["^1G",["^6X",["^1G",[["~$f"]]]]],"^6[","Returns an Interceptor which will run the given function `f` in the `:after`\n  position.  \n   \n  `f` is called with two arguments: `db` and `v`, and is expected to\n  return a modified `db`.\n\n  Unlike the `after` interceptor which is only about side effects, `enrich`\n  expects `f` to process and alter the given `db` coeffect in some useful way,\n  contributing to the derived data, flowing vibe.\n\n  #### Example Use:\n\n  Imagine that todomvc needed to do duplicate detection - if any two todos had\n  the same text, then highlight their background, and report them via a warning\n  at the bottom of the panel.\n\n  Almost any user action (edit text, add new todo, remove a todo) requires a\n  complete reassessment of duplication errors and warnings. Eg: that edit\n  just made might have introduced a new duplicate, or removed one. Same with\n  any todo removal. So we need to re-calculate warnings after any CRUD events\n  associated with the todos list.\n\n  Unless we are careful, we might end up coding subtly different checks\n  for each kind of CRUD operation.  The duplicates check made after\n  'delete todo' event might be subtly different to that done after an\n  editing operation. Nice and efficient, but fiddly. A bug generator\n  approach.\n\n  So, instead, we create an `f` which recalculates ALL warnings from scratch\n  every time there is ANY change. It will inspect all the todos, and\n  reset ALL FLAGS every time (overwriting what was there previously)\n  and fully recalculate the list of duplicates (displayed at the bottom?).\n\n  <a href=\"https://twitter.com/nathanmarz/status/879722740776939520\" target=\"_blank\">https://twitter.com/nathanmarz/status/879722740776939520</a>\n\n  By applying `f` in an `:enrich` interceptor, after every CRUD event,\n  we keep the handlers simple and yet we ensure this important step\n  (of getting warnings right) is not missed on any change.\n\n  We can test `f` easily - it is a pure function - independently of\n  any CRUD operation.\n\n  This brings huge simplicity at the expense of some re-computation\n  each time. This may be a very satisfactory trade-off in many cases."],"^G","^2G","^6","re_frame/core.cljc","^:",13,"^74",["^1G",[["~$f"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",590,"^7:","~$cljs.core/IMap","^9",590,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["~$f"]]]]],"^6[","Returns an Interceptor which will run the given function `f` in the `:after`\n  position.  \n   \n  `f` is called with two arguments: `db` and `v`, and is expected to\n  return a modified `db`.\n\n  Unlike the `after` interceptor which is only about side effects, `enrich`\n  expects `f` to process and alter the given `db` coeffect in some useful way,\n  contributing to the derived data, flowing vibe.\n\n  #### Example Use:\n\n  Imagine that todomvc needed to do duplicate detection - if any two todos had\n  the same text, then highlight their background, and report them via a warning\n  at the bottom of the panel.\n\n  Almost any user action (edit text, add new todo, remove a todo) requires a\n  complete reassessment of duplication errors and warnings. Eg: that edit\n  just made might have introduced a new duplicate, or removed one. Same with\n  any todo removal. So we need to re-calculate warnings after any CRUD events\n  associated with the todos list.\n\n  Unless we are careful, we might end up coding subtly different checks\n  for each kind of CRUD operation.  The duplicates check made after\n  'delete todo' event might be subtly different to that done after an\n  editing operation. Nice and efficient, but fiddly. A bug generator\n  approach.\n\n  So, instead, we create an `f` which recalculates ALL warnings from scratch\n  every time there is ANY change. It will inspect all the todos, and\n  reset ALL FLAGS every time (overwriting what was there previously)\n  and fully recalculate the list of duplicates (displayed at the bottom?).\n\n  <a href=\"https://twitter.com/nathanmarz/status/879722740776939520\" target=\"_blank\">https://twitter.com/nathanmarz/status/879722740776939520</a>\n\n  By applying `f` in an `:enrich` interceptor, after every CRUD event,\n  we keep the handlers simple and yet we ensure this important step\n  (of getting warnings right) is not missed on any change.\n\n  We can test `f` easily - it is a pure function - independently of\n  any CRUD operation.\n\n  This brings huge simplicity at the expense of some re-computation\n  each time. This may be a very satisfactory trade-off in many cases."],"~$reg-sub-raw",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",297,"^8",7,"^9",297,"^:",18,"^6W",["^1G",["^6X",["^1G",[["~$query-id","~$handler-fn"]]]]],"^6[","This is a low level, advanced function.  You should probably be\n  using `reg-sub` instead.\n\n  Some explanation is available in the docs at\n  <a href=\"http://day8.github.io/re-frame/flow-mechanics/\" target=\"_blank\">http://day8.github.io/re-frame/flow-mechanics/</a>"],"^G","^2P","^6","re_frame/core.cljc","^:",18,"^74",["^1G",[["^7B","^7C"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",297,"^7:","^79","^9",297,"^73",2,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7B","^7C"]]]]],"^6[","This is a low level, advanced function.  You should probably be\n  using `reg-sub` instead.\n\n  Some explanation is available in the docs at\n  <a href=\"http://day8.github.io/re-frame/flow-mechanics/\" target=\"_blank\">http://day8.github.io/re-frame/flow-mechanics/</a>"],"~$subscribe",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",211,"^8",7,"^9",211,"^:",16,"^6W",["^1G",["^6X",["^1G",[["~$query"],["^7E","~$dynv"]]]]],"^6[","Given a `query` vector, returns a Reagent `reaction` which will, over\n  time, reactively deliver a stream of values. So, in FRP-ish terms,\n  it returns a `Signal`.\n\n  To obtain the current value from the Signal, it must be dereferenced: \n  \n      (let [signal (subscribe [:items])\n            value  (deref signal)]     ;; could be written as @signal\n        ...)\n   \n   which is typically written tersely as simple:\n   \n      (let [items  @(subscribe [:items])] \n        ...)\n      \n\n  `query` is a vector of at least one element. The first element is the\n  `query-id`, typically a namespaced keyword. The rest of the vector's\n  elements are optional, additional values which parameterise the query\n  performed.\n\n  `dynv` is an optional 3rd argument, which is a vector of further input\n  signals (atoms, reactions, etc), NOT values. This argument exists for\n  historical reasons and is borderline deprecated these days.\n\n  **Example Usage**:\n\n      (subscribe [:items])\n      (subscribe [:items \"blue\" :small])\n      (subscribe [:items {:colour \"blue\"  :size :small}])\n \n  Note: for any given call to `subscribe` there must have been a previous call\n  to `reg-sub`, registering the query handler (functions) associated with \n  `query-id`.\n\n  **Hint**\n\n  When used in a view function BE SURE to `deref` the returned value.\n  In fact, to avoid any mistakes, some prefer to define:\n  \n      (def <sub  (comp deref re-frame.core/subscribe))\n \n  And then, within their views, they call  `(<sub [:items :small])` rather\n  than using `subscribe` directly.\n\n  **De-duplication**\n\n  Two, or more, concurrent subscriptions for the same query will \n  source reactive updates from the one executing handler.\n      \n  See also: `reg-sub`\n  ","^70",["^ ","^71",false,"^72",2,"^73",2,"^74",[["^7E"],["^7E","^7F"]],"^6W",["^1G",[["^7E"],["^7E","^7F"]]],"^75",["^1G",[null,null]]]],"^G","^2S","^6","re_frame/core.cljc","^:",16,"^70",["^ ","^71",false,"^72",2,"^73",2,"^74",[["^7E"],["^7E","^7F"]],"^6W",["^1G",[["^7E"],["^7E","^7F"]]],"^75",["^1G",[null,null]]],"^74",[["^7E"],["^7E","^7F"]],"^76",null,"^72",2,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",1,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",2,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",211,"^9",211,"^73",2,"^7;",true,"^6W",["^1G",[["^7E"],["^7E","^7F"]]],"^6[","Given a `query` vector, returns a Reagent `reaction` which will, over\n  time, reactively deliver a stream of values. So, in FRP-ish terms,\n  it returns a `Signal`.\n\n  To obtain the current value from the Signal, it must be dereferenced: \n  \n      (let [signal (subscribe [:items])\n            value  (deref signal)]     ;; could be written as @signal\n        ...)\n   \n   which is typically written tersely as simple:\n   \n      (let [items  @(subscribe [:items])] \n        ...)\n      \n\n  `query` is a vector of at least one element. The first element is the\n  `query-id`, typically a namespaced keyword. The rest of the vector's\n  elements are optional, additional values which parameterise the query\n  performed.\n\n  `dynv` is an optional 3rd argument, which is a vector of further input\n  signals (atoms, reactions, etc), NOT values. This argument exists for\n  historical reasons and is borderline deprecated these days.\n\n  **Example Usage**:\n\n      (subscribe [:items])\n      (subscribe [:items \"blue\" :small])\n      (subscribe [:items {:colour \"blue\"  :size :small}])\n \n  Note: for any given call to `subscribe` there must have been a previous call\n  to `reg-sub`, registering the query handler (functions) associated with \n  `query-id`.\n\n  **Hint**\n\n  When used in a view function BE SURE to `deref` the returned value.\n  In fact, to avoid any mistakes, some prefer to define:\n  \n      (def <sub  (comp deref re-frame.core/subscribe))\n \n  And then, within their views, they call  `(<sub [:items :small])` rather\n  than using `subscribe` directly.\n\n  **De-duplication**\n\n  Two, or more, concurrent subscriptions for the same query will \n  source reactive updates from the one executing handler.\n      \n  See also: `reg-sub`\n  "],"~$reg-global-interceptor",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",701,"^8",7,"^9",701,"^:",29,"^6W",["^1G",["^6X",["^1G",[["^11"]]]]],"^6[","Registers the given `interceptor` as a global interceptor. Global interceptors are\n   included in the processing chain of every event.\n\n   When you register an event handler, you have the option of supplying an\n   interceptor chain. Any global interceptors you register are effectively\n   prepending to this chain.\n\n   Global interceptors are run in the order that they are registered."],"^G","^3S","^6","re_frame/core.cljc","^:",29,"^74",["^1G",[["^11"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",701,"^7:",["^F",[null,"^79"]],"^9",701,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^11"]]]]],"^6[","Registers the given `interceptor` as a global interceptor. Global interceptors are\n   included in the processing chain of every event.\n\n   When you register an event handler, you have the option of supplying an\n   interceptor chain. Any global interceptors you register are effectively\n   prepending to this chain.\n\n   Global interceptors are run in the order that they are registered."],"~$assoc-coeffect",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",778,"^8",7,"^9",778,"^:",21,"^6W",["^1G",["^6X",["^1G",[["~$context","~$key","~$value"]]]]],"^6[","A utility function, typically used when writing an interceptor's `:before` function.\n\n   Adds or updates a key/value pair in the `:coeffects` map within `context`. "],"^G","^29","^6","re_frame/core.cljc","^:",21,"^74",["^1G",[["^7I","^7J","^7K"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",778,"^7:",["^F",["~$clj","^79"]],"^9",778,"^73",3,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7I","^7J","^7K"]]]]],"^6[","A utility function, typically used when writing an interceptor's `:before` function.\n\n   Adds or updates a key/value pair in the `:coeffects` map within `context`. "],"~$register-sub",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^:",19,"^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",["^6Z"]]],"^6W",["^1G",[["~$&","^6Z"]]],"^75",["^1G",[null]]],"^8",7,"^7",941,"~:deprecated","0.8.0","^9",941,"^6W",["^1G",["^6X",["^1G",[["~$&","^6Z"]]]]],"^6[","Deprecated. Use `reg-sub-raw` instead."],"^G","^28","^6","re_frame/core.cljc","^:",19,"^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",["^6Z"]]],"^6W",["^1G",[["~$&","^6Z"]]],"^75",["^1G",[null]]],"^74",[["^1G",["^6Z"]]],"^76",null,"^72",0,"^75",["^1G",[null]],"^8",1,"^71",true,"^77",[["^ ","^72",0,"^71",true,"^78","^79"]],"^7",941,"^7N","0.8.0","^7:","^79","^9",941,"^73",0,"^7;",true,"^6W",["^1G",[["~$&","^6Z"]]],"^6[","Deprecated. Use `reg-sub-raw` instead."],"~$purge-event-queue",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",892,"^8",7,"^9",892,"^:",24,"^6W",["^1G",["^6X",["^1G",[[]]]]],"^6[","Removes all events currently queued for processing"],"^G","^30","^6","re_frame/core.cljc","^:",24,"^74",["^1G",[[]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",892,"^7:","^79","^9",892,"^73",0,"^7;",true,"^6W",["^1G",["^6X",["^1G",[[]]]]],"^6[","Removes all events currently queued for processing"],"~$remove-post-event-callback",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",924,"^8",7,"^9",924,"^:",33,"^6W",["^1G",["^6X",["^1G",[["~$id"]]]]],"^6[","Unregisters a post event callback function, identified by `id`. \n   \n  Such a function must have been previously registered via `add-post-event-callback`"],"^G","^21","^6","re_frame/core.cljc","^:",33,"^74",["^1G",[["^7Q"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",924,"^7:","^79","^9",924,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7Q"]]]]],"^6[","Unregisters a post event callback function, identified by `id`. \n   \n  Such a function must have been previously registered via `add-post-event-callback`"],"~$path",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",559,"^8",7,"^9",559,"^:",11,"^6W",["^1G",["^6X",["^1G",[["~$&","^6Z"]]]]],"^6[","Returns an interceptor which acts somewhat like `clojure.core/update-in`, in the sense that \n  the event handler is given a specific part of `app-db` to change, not all of `app-db`. \n   \n  The interceptor has both a `:before` and `:after` functions. The `:before` replaces  \n  the `:db` key within coeffects with a sub-path within `app-db`. The `:after` reverses the process, \n  and it grafts the handler's return value back into db, at the right path.\n\n  Examples:\n\n      (path :some :path)\n      (path [:some :path])\n      (path [:some :path] :to :here)\n      (path [:some :path] [:to] :here)\n\n  Example Use:\n\n      (reg-event-db\n        :event-id\n        (path [:a :b])  ;; <-- used here, in interceptor chain\n        (fn [b v]       ;; 1st arg is not db. Is the value from path [:a :b] within db\n          ... new-b))   ;; returns a new value for that path (not the entire db)\n\n  Notes:\n  \n    1. `path` may appear more than once in an interceptor chain. Progressive narrowing.\n    2. if `:effects` contains no `:db` effect, can't graft a value back in.\n  ","^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",["^6Z"]]],"^6W",["^1G",[["~$&","^6Z"]]],"^75",["^1G",[null]]]],"^G","^3W","^6","re_frame/core.cljc","^:",11,"^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",["^6Z"]]],"^6W",["^1G",[["~$&","^6Z"]]],"^75",["^1G",[null]]],"^74",[["^1G",["^6Z"]]],"^76",null,"^72",0,"^75",["^1G",[null]],"^8",1,"^71",true,"^77",[["^ ","^72",0,"^71",true,"^78","^79"]],"^7",559,"^7:","^79","^9",559,"^73",0,"^7;",true,"^6W",["^1G",[["~$&","^6Z"]]],"^6[","Returns an interceptor which acts somewhat like `clojure.core/update-in`, in the sense that \n  the event handler is given a specific part of `app-db` to change, not all of `app-db`. \n   \n  The interceptor has both a `:before` and `:after` functions. The `:before` replaces  \n  the `:db` key within coeffects with a sub-path within `app-db`. The `:after` reverses the process, \n  and it grafts the handler's return value back into db, at the right path.\n\n  Examples:\n\n      (path :some :path)\n      (path [:some :path])\n      (path [:some :path] :to :here)\n      (path [:some :path] [:to] :here)\n\n  Example Use:\n\n      (reg-event-db\n        :event-id\n        (path [:a :b])  ;; <-- used here, in interceptor chain\n        (fn [b v]       ;; 1st arg is not db. Is the value from path [:a :b] within db\n          ... new-b))   ;; returns a new value for that path (not the entire db)\n\n  Notes:\n  \n    1. `path` may appear more than once in an interceptor chain. Progressive narrowing.\n    2. if `:effects` contains no `:db` effect, can't graft a value back in.\n  "],"~$reg-sub",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",69,"^8",7,"^9",69,"^:",14,"^6W",["^1G",["^6X",["^1G",[["^7B","~$&","^6Z"]]]]],"^6[","A call to `reg-sub` associates a `query-id` WITH two functions.\n   \n  The two functions provide 'a mechanism' for creating a node \n  in the Signal Graph. When a node of type `query-id` is needed, \n  the two functions can be used to create it.\n  \n  The three arguments are: \n   \n  - `query-id` - typically a namespaced keyword (later used in subscribe)\n  - optionally, an `input signals` function which returns the input data\n    flows required by this kind of node. \n  - a `computation function` which computes the value (output) of the \n    node (from the input data flows)\n     \n  Later, during app execution, a call to `(subscribe [:sub-id 3 :blue])`,\n  will trigger the need for a new `:sub-id` Signal Graph node (matching the \n  query `[:sub-id 3 :blue]`). And, to create that node the two functions \n  associated with `:sub-id` will be looked up and used.\n\n  Just to be clear: calling `reg-sub` does not immediately create a node. \n  It only registers 'a mechanism' (the two functions) by which nodes \n  can be created later, when a node is bought into existence by the \n  use of `subscribe` in a `View Function`.\n\n  The `computation function` is expected to take two arguments:\n  \n    - `input-values` - the values which flow into this node (how is it wierd into the graph?)\n    - `query-vector` - the vector given to `subscribe`\n  \n  and it returns a computed value (which then becomes the output of the node)\n\n  When `computation function` is called, the 2nd `query-vector` argument will be that \n  vector supplied to the `subscribe`. So, if the call was `(subscribe [:sub-id 3 :blue])`,\n  then the `query-vector` supplied to the computaton function will be `[:sub-id 3 :blue]`.\n\n  The argument(s) supplied to `reg-sub` between `query-id` and the `computation-function` \n  can vary in 3 ways, but whatever is there defines the `input signals` part \n  of `the mechanism`, specifying what input values \"flow into\" the \n  `computation function` (as the 1st argument) when it is called.\n\n  So, `reg-sub` can be called in one of three ways, because there are three ways \n  to define the input signals part. But note, the 2nd method, in which a \n  `signals function` is explicitly supplied, is the most canonical and \n  instructive. The other two are really just sugary variations.\n\n  **First variation** - no input signal function given:\n\n      (reg-sub\n        :query-id\n        a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n     In the absence of an explicit `signals function`, the node's input signal defaults to `app-db`\n     and, as a result, the value within `app-db` (a map) is\n     is given as the 1st argument when `a-computation-fn` is called.\n\n\n  **Second variation** - a signal function is explicitly supplied:\n\n      (reg-sub\n        :query-id\n        signal-fn     ;; <-- here\n        computation-fn)\n\n  This is the most canonical and instructive of the three variations.\n\n  When a node is created from the template, the `signal function` will be called and it\n  is expected to return the input signal(s) as either a singleton, if there is only\n  one, or a sequence if there are many, or a map with the signals as the values.\n\n  The current values of the returned signals will be supplied as the 1st argument to\n  the `a-computation-fn` when it is called - and subject to what this `signal-fn` returns,\n  this value will be either a singleton, sequence or map of them (paralleling\n  the structure returned by the `signal function`).\n\n  This example `signal function` returns a 2-vector of input signals.\n\n      (fn [query-vec dynamic-vec]\n         [(subscribe [:a-sub])\n          (subscribe [:b-sub])])\n\n  The associated computation function must be written\n  to expect a 2-vector of values for its first argument:\n\n      (fn [[a b] query-vec]     ;; 1st argument is a seq of two values\n        ....)\n\n  If, on the other hand, the signal function was simpler and returned a singleton, like this:\n\n     (fn [query-vec dynamic-vec]\n       (subscribe [:a-sub]))      ;; <-- returning a singleton\n\n  then the associated computation function must be written to expect a single value\n  as the 1st argument:\n\n      (fn [a query-vec]       ;; 1st argument is a single value\n         ...)\n\n  Further Note: variation #1 above, in which an `input-fn` was not supplied, like this:\n\n      (reg-sub\n        :query-id\n        a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n  is the equivalent of using this\n  2nd variation and explicitly suppling a `signal-fn` which returns `app-db`:\n\n      (reg-sub\n        :query-id\n        (fn [_ _]  re-frame/app-db)   ;; <--- explicit signal-fn\n        a-computation-fn)             ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n  **Third variation** - syntax Sugar\n\n      (reg-sub\n        :a-b-sub\n        :<- [:a-sub]\n        :<- [:b-sub]\n        (fn [[a b] query-vec]    ;; 1st argument is a seq of two values\n          {:a a :b b}))\n\n  This 3rd variation is just syntactic sugar for the 2nd.  Instead of providing an\n  `signals-fn` you provide one or more pairs of `:<-` and a subscription vector.\n\n  If you supply only one pair a singleton will be supplied to the computation function,\n  as if you had supplied a `signal-fn` returning only a single value:\n\n\n      (reg-sub\n        :a-sub\n        :<- [:a-sub]\n        (fn [a query-vec]      ;; only one pair, so 1st argument is a single value\n          ...))\n\n  For further understanding, read the tutorials, and look at the detailed comments in\n  /examples/todomvc/src/subs.cljs.\n        \n  See also: `subscribe`\n  ","^70",["^ ","^71",true,"^72",1,"^73",1,"^74",[["^1G",["^7B","^6Z"]]],"^6W",["^1G",[["^7B","~$&","^6Z"]]],"^75",["^1G",[null]]]],"^G","^3K","^6","re_frame/core.cljc","^:",14,"^70",["^ ","^71",true,"^72",1,"^73",1,"^74",[["^1G",["^7B","^6Z"]]],"^6W",["^1G",[["^7B","~$&","^6Z"]]],"^75",["^1G",[null]]],"^74",[["^1G",["^7B","^6Z"]]],"^76",null,"^72",1,"^75",["^1G",[null]],"^8",1,"^71",true,"^77",[["^ ","^72",1,"^71",true,"^78","^79"]],"^7",69,"^7:","^79","^9",69,"^73",1,"^7;",true,"^6W",["^1G",[["^7B","~$&","^6Z"]]],"^6[","A call to `reg-sub` associates a `query-id` WITH two functions.\n   \n  The two functions provide 'a mechanism' for creating a node \n  in the Signal Graph. When a node of type `query-id` is needed, \n  the two functions can be used to create it.\n  \n  The three arguments are: \n   \n  - `query-id` - typically a namespaced keyword (later used in subscribe)\n  - optionally, an `input signals` function which returns the input data\n    flows required by this kind of node. \n  - a `computation function` which computes the value (output) of the \n    node (from the input data flows)\n     \n  Later, during app execution, a call to `(subscribe [:sub-id 3 :blue])`,\n  will trigger the need for a new `:sub-id` Signal Graph node (matching the \n  query `[:sub-id 3 :blue]`). And, to create that node the two functions \n  associated with `:sub-id` will be looked up and used.\n\n  Just to be clear: calling `reg-sub` does not immediately create a node. \n  It only registers 'a mechanism' (the two functions) by which nodes \n  can be created later, when a node is bought into existence by the \n  use of `subscribe` in a `View Function`.\n\n  The `computation function` is expected to take two arguments:\n  \n    - `input-values` - the values which flow into this node (how is it wierd into the graph?)\n    - `query-vector` - the vector given to `subscribe`\n  \n  and it returns a computed value (which then becomes the output of the node)\n\n  When `computation function` is called, the 2nd `query-vector` argument will be that \n  vector supplied to the `subscribe`. So, if the call was `(subscribe [:sub-id 3 :blue])`,\n  then the `query-vector` supplied to the computaton function will be `[:sub-id 3 :blue]`.\n\n  The argument(s) supplied to `reg-sub` between `query-id` and the `computation-function` \n  can vary in 3 ways, but whatever is there defines the `input signals` part \n  of `the mechanism`, specifying what input values \"flow into\" the \n  `computation function` (as the 1st argument) when it is called.\n\n  So, `reg-sub` can be called in one of three ways, because there are three ways \n  to define the input signals part. But note, the 2nd method, in which a \n  `signals function` is explicitly supplied, is the most canonical and \n  instructive. The other two are really just sugary variations.\n\n  **First variation** - no input signal function given:\n\n      (reg-sub\n        :query-id\n        a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n     In the absence of an explicit `signals function`, the node's input signal defaults to `app-db`\n     and, as a result, the value within `app-db` (a map) is\n     is given as the 1st argument when `a-computation-fn` is called.\n\n\n  **Second variation** - a signal function is explicitly supplied:\n\n      (reg-sub\n        :query-id\n        signal-fn     ;; <-- here\n        computation-fn)\n\n  This is the most canonical and instructive of the three variations.\n\n  When a node is created from the template, the `signal function` will be called and it\n  is expected to return the input signal(s) as either a singleton, if there is only\n  one, or a sequence if there are many, or a map with the signals as the values.\n\n  The current values of the returned signals will be supplied as the 1st argument to\n  the `a-computation-fn` when it is called - and subject to what this `signal-fn` returns,\n  this value will be either a singleton, sequence or map of them (paralleling\n  the structure returned by the `signal function`).\n\n  This example `signal function` returns a 2-vector of input signals.\n\n      (fn [query-vec dynamic-vec]\n         [(subscribe [:a-sub])\n          (subscribe [:b-sub])])\n\n  The associated computation function must be written\n  to expect a 2-vector of values for its first argument:\n\n      (fn [[a b] query-vec]     ;; 1st argument is a seq of two values\n        ....)\n\n  If, on the other hand, the signal function was simpler and returned a singleton, like this:\n\n     (fn [query-vec dynamic-vec]\n       (subscribe [:a-sub]))      ;; <-- returning a singleton\n\n  then the associated computation function must be written to expect a single value\n  as the 1st argument:\n\n      (fn [a query-vec]       ;; 1st argument is a single value\n         ...)\n\n  Further Note: variation #1 above, in which an `input-fn` was not supplied, like this:\n\n      (reg-sub\n        :query-id\n        a-computation-fn)   ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n  is the equivalent of using this\n  2nd variation and explicitly suppling a `signal-fn` which returns `app-db`:\n\n      (reg-sub\n        :query-id\n        (fn [_ _]  re-frame/app-db)   ;; <--- explicit signal-fn\n        a-computation-fn)             ;; has signature:  (fn [db query-vec]  ... ret-value)\n\n  **Third variation** - syntax Sugar\n\n      (reg-sub\n        :a-b-sub\n        :<- [:a-sub]\n        :<- [:b-sub]\n        (fn [[a b] query-vec]    ;; 1st argument is a seq of two values\n          {:a a :b b}))\n\n  This 3rd variation is just syntactic sugar for the 2nd.  Instead of providing an\n  `signals-fn` you provide one or more pairs of `:<-` and a subscription vector.\n\n  If you supply only one pair a singleton will be supplied to the computation function,\n  as if you had supplied a `signal-fn` returning only a single value:\n\n\n      (reg-sub\n        :a-sub\n        :<- [:a-sub]\n        (fn [a query-vec]      ;; only one pair, so 1st argument is a single value\n          ...))\n\n  For further understanding, read the tutorials, and look at the detailed comments in\n  /examples/todomvc/src/subs.cljs.\n        \n  See also: `subscribe`\n  "],"~$make-restore-fn",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",865,"^8",7,"^9",865,"^:",22,"^6W",["^1G",["^6X",["^1G",[[]]]]],"^6[","This is a utility function, typically used in testing.\n\n  It checkpoints the current state of re-frame and returns a function which, when\n  later called, will restore re-frame to the checkpointed state.\n\n  The checkpoint includes `app-db`, all registered handlers and all subscriptions.\n  "],"^G","^3H","^6","re_frame/core.cljc","^:",22,"^74",["^1G",[[]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",865,"^7:","~$function","^9",865,"^73",0,"^7;",true,"^6W",["^1G",["^6X",["^1G",[[]]]]],"^6[","This is a utility function, typically used in testing.\n\n  It checkpoints the current state of re-frame and returns a function which, when\n  later called, will restore re-frame to the checkpointed state.\n\n  The checkpoint includes `app-db`, all registered handlers and all subscriptions.\n  "],"~$clear-fx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",333,"^8",7,"^9",333,"^:",15,"^6W",["^1G",["^6X",["^1G",[[],["^7Q"]]]]],"^6[","Unregisters effect handlers (presumably registered previously via the use of `reg-fx`). \n   \n  When called with no args, it will unregister all currently registered effect handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  effect handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\n  ","^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]]],"^G","^39","^6","re_frame/core.cljc","^:",15,"^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]],"^74",[[],["^7Q"]],"^76",null,"^72",1,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",0,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",1,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",333,"^9",333,"^73",1,"^7;",true,"^6W",["^1G",[[],["^7Q"]]],"^6[","Unregisters effect handlers (presumably registered previously via the use of `reg-fx`). \n   \n  When called with no args, it will unregister all currently registered effect handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  effect handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\n  "],"~$get-effect",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",785,"^8",7,"^9",785,"^:",17,"^6W",["^1G",["^6X",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","~$not-found"]]]]],"^6[","A utility function, used when writing interceptors, typically within an `:after` function.\n\n   When called with one argument, returns the `:effects` map from the `context`.\n\n   When called with two or three arguments, behaves like `clojure.core/get` and\n   returns the value mapped to `key` in the effects map, `not-found` or\n   `nil` if `key` is not present.","^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]],"^6W",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]],"^75",["^1G",[null,null,null]]]],"^G","^31","^6","re_frame/core.cljc","^:",17,"^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]],"^6W",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]],"^75",["^1G",[null,null,null]]],"^74",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]],"^76",null,"^72",3,"^75",["^1G",[null,null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",1,"^71",false,"^78","^79"],["^ ","^72",2,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",3,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",785,"^9",785,"^73",3,"^7;",true,"^6W",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]],"^6[","A utility function, used when writing interceptors, typically within an `:after` function.\n\n   When called with one argument, returns the `:effects` map from the `context`.\n\n   When called with two or three arguments, behaves like `clojure.core/get` and\n   returns the value mapped to `key` in the effects map, `not-found` or\n   `nil` if `key` is not present."],"~$reg-event-db",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",437,"^8",7,"^9",437,"^:",19,"^6W",["^1G",["^6X",["^1G",[["^7Q","~$handler"],["^7Q","~$interceptors","^7Z"]]]]],"^6[","Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n\n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (db event) -> db\n    - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n\n  Example Usage:\n\n      (reg-event-db \n        :token \n        (fn [db event]\n          (assoc db :some-key (get event 2)))  ;; return updated db\n\n  Or perhaps:\n\n      (reg-event-db\n        :namespaced/id           ;; <-- namespaced keywords are often used\n        [one two three]          ;; <-- a seq of interceptors\n        (fn [db [_ arg1 arg2]]   ;; <-- event vector is destructured\n          (-> db \n            (dissoc arg1)\n            (update :key + arg2))))   ;; return updated db\n  ","^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^75",["^1G",[null,null]]]],"^G","^2O","^6","re_frame/core.cljc","^:",19,"^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^75",["^1G",[null,null]]],"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^76",null,"^72",3,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",2,"^71",false,"^78","^79"],["^ ","^72",3,"^71",false,"^78","^79"]],"^7",437,"^9",437,"^73",3,"^7;",true,"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^6[","Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n\n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (db event) -> db\n    - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n\n  Example Usage:\n\n      (reg-event-db \n        :token \n        (fn [db event]\n          (assoc db :some-key (get event 2)))  ;; return updated db\n\n  Or perhaps:\n\n      (reg-event-db\n        :namespaced/id           ;; <-- namespaced keywords are often used\n        [one two three]          ;; <-- a seq of interceptors\n        (fn [db [_ arg1 arg2]]   ;; <-- event vector is destructured\n          (-> db \n            (dissoc arg1)\n            (update :key + arg2))))   ;; return updated db\n  "],"~$dispatch-sync",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",41,"^8",7,"^9",41,"^:",20,"^6W",["^1G",["^6X",["^1G",[["~$event"]]]]],"^6[","Synchronously (immediately) process `event`. It does **not** queue\n  the event for handling later as `dispatch` does. \n  \n  `event` is a vector and the first element is typically a keyword \n  which identifies the kind of event.\n\n  It is an error to use `dispatch-sync` within an event handler because \n  you can't immediately process an new event when one is already\n  part way through being processed.\n\n  Generally, avoid using this function, and instead, use `dispatch`. \n  Only use it in the narrow set of cases where any delay in \n  processing is a problem:\n\n    1. the `:on-change` handler of a text field where we are expecting fast typing\n    2. when initialising your app - see 'main' in examples/todomvc/src/core.cljs\n    3. in a unit test where immediate, synchronous processing is useful\n\n  Usage:\n\n      (dispatch-sync [:sing :falsetto \"piano accordion\"])\n  "],"^G","^2Q","^6","re_frame/core.cljc","^:",20,"^74",["^1G",[["^81"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",41,"^7:","~$clj-nil","^9",41,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^81"]]]]],"^6[","Synchronously (immediately) process `event`. It does **not** queue\n  the event for handling later as `dispatch` does. \n  \n  `event` is a vector and the first element is typically a keyword \n  which identifies the kind of event.\n\n  It is an error to use `dispatch-sync` within an event handler because \n  you can't immediately process an new event when one is already\n  part way through being processed.\n\n  Generally, avoid using this function, and instead, use `dispatch`. \n  Only use it in the narrow set of cases where any delay in \n  processing is a problem:\n\n    1. the `:on-change` handler of a text field where we are expecting fast typing\n    2. when initialising your app - see 'main' in examples/todomvc/src/core.cljs\n    3. in a unit test where immediate, synchronous processing is useful\n\n  Usage:\n\n      (dispatch-sync [:sing :falsetto \"piano accordion\"])\n  "],"~$clear-event",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",514,"^8",7,"^9",514,"^:",18,"^6W",["^1G",["^6X",["^1G",[[],["^7Q"]]]]],"^6[","Unregisters event handlers (presumably registered previously via the use of `reg-event-db` or `reg-event-fx`). \n   \n  When called with no args, it will unregister all currently registered event handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  event handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.","^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]]],"^G","^27","^6","re_frame/core.cljc","^:",18,"^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]],"^74",[[],["^7Q"]],"^76",null,"^72",1,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",0,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",1,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",514,"^9",514,"^73",1,"^7;",true,"^6W",["^1G",[[],["^7Q"]]],"^6[","Unregisters event handlers (presumably registered previously via the use of `reg-event-db` or `reg-event-fx`). \n   \n  When called with no args, it will unregister all currently registered event handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  event handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration."],"~$->interceptor",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",727,"^8",7,"^9",727,"^:",20,"^6W",["^1G",["^6X",["^1G",[["~$&",["^ ","^1I","~$m","~:keys",["^7Q","~$before","~$after"]]]]]]],"^6[","A utility function for creating interceptors.\n\n  Accepts three optional, named arguments:\n\n     - `:id` - an id for the interceptor (decorative only)\n     - `:before` - the interceptor's before function\n     - `:after`  - the interceptor's after function\n\n  Example use:\n\n      (def my-interceptor\n        (->interceptor\n         :id     :my-interceptor\n         :before (fn [context]\n                   ... modifies and returns `context`)\n         :after  (fn [context] \n                   ... modifies and returns `context`)))\n   \n  Notes:\n  \n    - `:before` functions modify and return their `context` argument. Sometimes they \n      only side effect, in which case, they'll perform the side effect and return\n      `context` unchanged.\n    - `:before` functions often modify the `:coeffects` map within `context` and, \n      if they do, then they should use the utility functions `get-coeffect` and \n      `assoc-coeffect`.\n    - `:after` functions modify and return their `context` argument. Sometimes they \n      only side effect, in which case, they'll perform the side effect and return \n      `context` unchanged.\n    - `:after` functions often modify the `:effects` map within `context` and, \n      if they do, then they should use the utility functions `get-effect`\n      and `assoc-effect`","^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",[["^ ","^1I","~$m","^85",["^7Q","^86","^87"]]]]],"^6W",["^1G",[["~$&",["^ ","^1I","~$m","^85",["^7Q","^86","^87"]]]]],"^75",["^1G",[null]]]],"^G","^3C","^6","re_frame/core.cljc","^:",20,"^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",[["^ ","^1I","~$m","^85",["^7Q","^86","^87"]]]]],"^6W",["^1G",[["~$&",["^ ","^1I","~$m","^85",["^7Q","^86","^87"]]]]],"^75",["^1G",[null]]],"^74",[["^1G",[["^ ","^1I","~$m","^85",["^7Q","^86","^87"]]]]],"^76",null,"^72",0,"^75",["^1G",[null]],"^8",1,"^71",true,"^77",[["^ ","^72",0,"^71",true,"^78","^79"]],"^7",727,"^7:","^79","^9",727,"^73",0,"^7;",true,"^6W",["^1G",[["~$&",["^ ","^1I","~$m","^85",["^7Q","^86","^87"]]]]],"^6[","A utility function for creating interceptors.\n\n  Accepts three optional, named arguments:\n\n     - `:id` - an id for the interceptor (decorative only)\n     - `:before` - the interceptor's before function\n     - `:after`  - the interceptor's after function\n\n  Example use:\n\n      (def my-interceptor\n        (->interceptor\n         :id     :my-interceptor\n         :before (fn [context]\n                   ... modifies and returns `context`)\n         :after  (fn [context] \n                   ... modifies and returns `context`)))\n   \n  Notes:\n  \n    - `:before` functions modify and return their `context` argument. Sometimes they \n      only side effect, in which case, they'll perform the side effect and return\n      `context` unchanged.\n    - `:before` functions often modify the `:coeffects` map within `context` and, \n      if they do, then they should use the utility functions `get-coeffect` and \n      `assoc-coeffect`.\n    - `:after` functions modify and return their `context` argument. Sometimes they \n      only side effect, in which case, they'll perform the side effect and return \n      `context` unchanged.\n    - `:after` functions often modify the `:effects` map within `context` and, \n      if they do, then they should use the utility functions `get-effect`\n      and `assoc-effect`"],"~$set-loggers!",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",822,"^8",7,"^9",822,"^:",19,"^6W",["^1G",["^6X",["^1G",[["~$new-loggers"]]]]],"^6[","re-frame outputs warnings and errors via the API function `console` \n   which, by default, delegates to `js/console`'s default implementation for \n  `log`, `error`, `warn`, `debug`, `group` and `groupEnd`. But, using this function,\n   you can override that behaviour with your own functions. \n\n  The argument `new-loggers` should be a map containing a subset of they keys \n  for the standard `loggers`, namely  `:log` `:error` `:warn` `:debug` `:group` \n  or `:groupEnd`.\n\n  Example Usage:\n\n      (defn my-logger      ;; my alternative logging function\n        [& args]\n        (post-it-somewhere (apply str args)))\n\n      ;; now install my alternative loggers\n      (re-frame.core/set-loggers!  {:warn my-logger :log my-logger})\n   "],"^G","^3F","^6","re_frame/core.cljc","^:",19,"^74",["^1G",[["^89"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",822,"^7:",["^F",[null,"^79"]],"^9",822,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^89"]]]]],"^6[","re-frame outputs warnings and errors via the API function `console` \n   which, by default, delegates to `js/console`'s default implementation for \n  `log`, `error`, `warn`, `debug`, `group` and `groupEnd`. But, using this function,\n   you can override that behaviour with your own functions. \n\n  The argument `new-loggers` should be a map containing a subset of they keys \n  for the standard `loggers`, namely  `:log` `:error` `:warn` `:debug` `:group` \n  or `:groupEnd`.\n\n  Example Usage:\n\n      (defn my-logger      ;; my alternative logging function\n        [& args]\n        (post-it-somewhere (apply str args)))\n\n      ;; now install my alternative loggers\n      (re-frame.core/set-loggers!  {:warn my-logger :log my-logger})\n   "],"~$inject-cofx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",361,"^8",7,"^9",361,"^:",18,"^6W",["^1G",["^6X",["^1G",[["^7Q"],["^7Q","^7K"]]]]],"^6[","Given an `id`, and an optional, arbitrary `value`, returns an interceptor\n  whose `:before` adds to the `:coeffects` (map) by calling a pre-registered\n  'coeffect handler' identified by the `id`.\n\n  The previous association of a `coeffect handler` with an `id` will have\n  happened via a call to `re-frame.core/reg-cofx` - generally on program startup.\n\n  Within the created interceptor, this 'looked up' `coeffect handler` will\n  be called (within the `:before`) with two arguments:\n\n  - the current value of `:coeffects`\n  - optionally, the originally supplied arbitrary `value`\n\n  This `coeffect handler` is expected to modify and return its first, `coeffects` argument.\n\n  **Example of `inject-cofx` and `reg-cofx` working together**\n\n\n  First - Early in app startup, you register a `coeffect handler` for `:datetime`:\n\n      (re-frame.core/reg-cofx\n        :datetime                        ;; usage  (inject-cofx :datetime)\n        (fn coeffect-handler\n          [coeffect]\n          (assoc coeffect :now (js/Date.))))   ;; modify and return first arg\n\n  Second - Later, add an interceptor to an -fx event handler, using `inject-cofx`:\n\n      (re-frame.core/reg-event-fx            ;; when registering an event handler\n        :event-id\n        [ ... (inject-cofx :datetime) ... ]  ;; <-- create an injecting interceptor\n        (fn event-handler\n          [coeffect event]\n            ;;... in here can access (:now coeffect) to obtain current datetime ... \n          )))\n\n  **Background**\n\n  `coeffects` are the input resources required by an event handler\n  to perform its job. The two most obvious ones are `db` and `event`.\n  But sometimes an event handler might need other resources.\n\n  Perhaps an event handler needs a random number or a GUID or the current\n  datetime. Perhaps it needs access to a DataScript database connection.\n\n  If an event handler directly accesses these resources, it stops being\n  pure and, consequently, it becomes harder to test, etc. So we don't\n  want that.\n\n  Instead, the interceptor created by this function is a way to 'inject'\n  'necessary resources' into the `:coeffects` (map) subsequently given\n  to the event handler at call time.\n          \n  See also `reg-cofx`\n  ","^70",["^ ","^71",false,"^72",2,"^73",2,"^74",[["^7Q"],["^7Q","^7K"]],"^6W",["^1G",[["^7Q"],["^7Q","^7K"]]],"^75",["^1G",[null,null]]]],"^G","^3D","^6","re_frame/core.cljc","^:",18,"^70",["^ ","^71",false,"^72",2,"^73",2,"^74",[["^7Q"],["^7Q","^7K"]],"^6W",["^1G",[["^7Q"],["^7Q","^7K"]]],"^75",["^1G",[null,null]]],"^74",[["^7Q"],["^7Q","^7K"]],"^76",null,"^72",2,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",1,"^71",false,"^78","^7@"],["^ ","^72",2,"^71",false,"^78","^7@"]],"^7",361,"^9",361,"^73",2,"^7;",true,"^6W",["^1G",[["^7Q"],["^7Q","^7K"]]],"^6[","Given an `id`, and an optional, arbitrary `value`, returns an interceptor\n  whose `:before` adds to the `:coeffects` (map) by calling a pre-registered\n  'coeffect handler' identified by the `id`.\n\n  The previous association of a `coeffect handler` with an `id` will have\n  happened via a call to `re-frame.core/reg-cofx` - generally on program startup.\n\n  Within the created interceptor, this 'looked up' `coeffect handler` will\n  be called (within the `:before`) with two arguments:\n\n  - the current value of `:coeffects`\n  - optionally, the originally supplied arbitrary `value`\n\n  This `coeffect handler` is expected to modify and return its first, `coeffects` argument.\n\n  **Example of `inject-cofx` and `reg-cofx` working together**\n\n\n  First - Early in app startup, you register a `coeffect handler` for `:datetime`:\n\n      (re-frame.core/reg-cofx\n        :datetime                        ;; usage  (inject-cofx :datetime)\n        (fn coeffect-handler\n          [coeffect]\n          (assoc coeffect :now (js/Date.))))   ;; modify and return first arg\n\n  Second - Later, add an interceptor to an -fx event handler, using `inject-cofx`:\n\n      (re-frame.core/reg-event-fx            ;; when registering an event handler\n        :event-id\n        [ ... (inject-cofx :datetime) ... ]  ;; <-- create an injecting interceptor\n        (fn event-handler\n          [coeffect event]\n            ;;... in here can access (:now coeffect) to obtain current datetime ... \n          )))\n\n  **Background**\n\n  `coeffects` are the input resources required by an event handler\n  to perform its job. The two most obvious ones are `db` and `event`.\n  But sometimes an event handler might need other resources.\n\n  Perhaps an event handler needs a random number or a GUID or the current\n  datetime. Perhaps it needs access to a DataScript database connection.\n\n  If an event handler directly accesses these resources, it stops being\n  pure and, consequently, it becomes harder to test, etc. So we don't\n  want that.\n\n  Instead, the interceptor created by this function is a way to 'inject'\n  'necessary resources' into the `:coeffects` (map) subsequently given\n  to the event handler at call time.\n          \n  See also `reg-cofx`\n  "],"~$clear-global-interceptor",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",713,"^8",7,"^9",713,"^:",31,"^6W",["^1G",["^6X",["^1G",[[],["^7Q"]]]]],"^6[","Unregisters global interceptors (presumably registered previously via the use of `reg-global-interceptor`). \n   \n  When called with no args, it will unregister all currently registered global interceptors. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  global interceptors, it will unregister the associated interceptor. Will produce a warning to \n  console if it finds no matching registration.","^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]]],"^G","^3P","^6","re_frame/core.cljc","^:",31,"^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]],"^74",[[],["^7Q"]],"^76",null,"^72",1,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",0,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",1,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",713,"^9",713,"^73",1,"^7;",true,"^6W",["^1G",[[],["^7Q"]]],"^6[","Unregisters global interceptors (presumably registered previously via the use of `reg-global-interceptor`). \n   \n  When called with no args, it will unregister all currently registered global interceptors. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  global interceptors, it will unregister the associated interceptor. Will produce a warning to \n  console if it finds no matching registration."],"~$get-coeffect",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",763,"^8",7,"^9",763,"^:",19,"^6W",["^1G",["^6X",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]]]],"^6[","A utility function, typically used when writing an interceptor's `:before` function.\n\n   When called with one argument, it returns the `:coeffects` map from with that `context`.\n\n   When called with two or three arguments, behaves like `clojure.core/get` and\n   returns the value mapped to `key` in the `:coeffects` map within `context`, `not-found` or\n   `nil` if `key` is not present.","^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]],"^6W",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]],"^75",["^1G",[null,null,null]]]],"^G","^2J","^6","re_frame/core.cljc","^:",19,"^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]],"^6W",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]],"^75",["^1G",[null,null,null]]],"^74",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]],"^76",null,"^72",3,"^75",["^1G",[null,null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",1,"^71",false,"^78","^79"],["^ ","^72",2,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",3,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",763,"^9",763,"^73",3,"^7;",true,"^6W",["^1G",[["^7I"],["^7I","^7J"],["^7I","^7J","^7X"]]],"^6[","A utility function, typically used when writing an interceptor's `:before` function.\n\n   When called with one argument, it returns the `:coeffects` map from with that `context`.\n\n   When called with two or three arguments, behaves like `clojure.core/get` and\n   returns the value mapped to `key` in the `:coeffects` map within `context`, `not-found` or\n   `nil` if `key` is not present."],"~$debug",["^ ","^5",["^ ","^6","re_frame/core.cljc","^7",529,"^8",6,"^9",529,"^:",11],"^G","^3Y","^6","re_frame/core.cljc","^:",11,"^8",1,"^7",529,"^9",529,"^78","^7@","^6[","An interceptor which logs/instruments an event handler's actions to\n  `js/console.debug`. See examples/todomvc/src/events.cljs for use.\n\n  Output includes:\n\n    1. the event vector\n    2. a `clojure.data/diff` of db, before vs after, which shows\n       the changes caused by the event handler. To understand the output,\n       you should understand:\n       <a href=\"https://clojuredocs.org/clojure.data/diff\" target=\"_blank\">https://clojuredocs.org/clojure.data/diff</a>.\n\n  You'd typically include this interceptor after (to the right of) any\n  `path` interceptor.\n\n  Warning:  calling `clojure.data/diff` on large, complex data structures\n  can be slow. So, you won't want this interceptor present in production\n  code. So, you should condition it out like this:\n\n      (re-frame.core/reg-event-db\n        :evt-id\n        [(when ^boolean goog.DEBUG re-frame.core/debug)]  ;; <-- conditional\n        (fn [db v]\n           ...))\n\n  To make this code fragment work, you'll also have to set `goog.DEBUG` to\n  `false` in your production builds. For an example, look in `project.clj` of /examples/todomvc.\n  "],"~$assoc-effect",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",800,"^8",7,"^9",800,"^:",19,"^6W",["^1G",["^6X",["^1G",[["^7I","^7J","^7K"]]]]],"^6[","A utility function, typically used when writing an interceptor's `:after` function.\n\n   Adds or updates a key/value pair in the `:effects` map within `context`. "],"^G","^2L","^6","re_frame/core.cljc","^:",19,"^74",["^1G",[["^7I","^7J","^7K"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",800,"^7:",["^F",["^7L","^79"]],"^9",800,"^73",3,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7I","^7J","^7K"]]]]],"^6[","A utility function, typically used when writing an interceptor's `:after` function.\n\n   Adds or updates a key/value pair in the `:effects` map within `context`. "],"~$enqueue",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",807,"^8",7,"^9",807,"^:",14,"^6W",["^1G",["^6X",["^1G",[["^7I","^7["]]]]],"^6[","A utility function, used when writing an interceptor's `:before` function.\n\n  Adds the given collection of `interceptors` to those already in `context's` \n  execution `:queue`. It returns the updated `context`.\n   \n  So, it provides a way for one Interceptor to add more interceptors to the \n  currently executing interceptor chain.\n  "],"^G","^3X","^6","re_frame/core.cljc","^:",14,"^74",["^1G",[["^7I","^7["]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",807,"^7:",["^F",["^7L","^79"]],"^9",807,"^73",2,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7I","^7["]]]]],"^6[","A utility function, used when writing an interceptor's `:before` function.\n\n  Adds the given collection of `interceptors` to those already in `context's` \n  execution `:queue`. It returns the updated `context`.\n   \n  So, it provides a way for one Interceptor to add more interceptors to the \n  currently executing interceptor chain.\n  "],"~$clear-cofx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",422,"^8",7,"^9",422,"^:",17,"^6W",["^1G",["^6X",["^1G",[[],["^7Q"]]]]],"^6[","Unregisters coeffect handlers (presumably registered previously via the use of `reg-cofx`). \n   \n  When called with no args, it will unregister all currently registered coeffect handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  coeffect handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.","^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]]],"^G","^34","^6","re_frame/core.cljc","^:",17,"^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7Q"]],"^6W",["^1G",[[],["^7Q"]]],"^75",["^1G",[null,null]]],"^74",[[],["^7Q"]],"^76",null,"^72",1,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",0,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",1,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",422,"^9",422,"^73",1,"^7;",true,"^6W",["^1G",[[],["^7Q"]]],"^6[","Unregisters coeffect handlers (presumably registered previously via the use of `reg-cofx`). \n   \n  When called with no args, it will unregister all currently registered coeffect handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  coeffect handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration."],"~$reg-event-ctx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",500,"^8",7,"^9",500,"^:",20,"^6W",["^1G",["^6X",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]]]],"^6[","Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n   \n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (context-map event-vector) -> context-map\n\n  This form of registration is seldomAt dinner wenever used.\n  ","^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^75",["^1G",[null,null]]]],"^G","^35","^6","re_frame/core.cljc","^:",20,"^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^75",["^1G",[null,null]]],"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^76",null,"^72",3,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",2,"^71",false,"^78","^79"],["^ ","^72",3,"^71",false,"^78","^79"]],"^7",500,"^9",500,"^73",3,"^7;",true,"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^6[","Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n   \n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (context-map event-vector) -> context-map\n\n  This form of registration is seldomAt dinner wenever used.\n  "],"~$reg-fx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",308,"^8",7,"^9",308,"^:",13,"^6W",["^1G",["^6X",["^1G",[["^7Q","^7Z"]]]]],"^6[","Register the given effect `handler` for the given `id`:\n\n    - `id` is keyword, often namespaced.\n    - `handler` is a side-effecting function which takes a single argument and whose return\n      value is ignored.\n\n  To use, first, associate `:effect2` with a handler:\n\n      (reg-fx\n         :effect2\n         (fn [value]\n            ... do something side-effect-y))\n\n  Then, later, if an event handler were to return this effects map:\n\n      {:effect2  [1 2]}\n\n  then the `handler` `fn` we registered previously, using `reg-fx`, will be\n  called with an argument of `[1 2]`.\n  "],"^G","^2[","^6","re_frame/core.cljc","^:",13,"^74",["^1G",[["^7Q","^7Z"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",308,"^7:","^79","^9",308,"^73",2,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7Q","^7Z"]]]]],"^6[","Register the given effect `handler` for the given `id`:\n\n    - `id` is keyword, often namespaced.\n    - `handler` is a side-effecting function which takes a single argument and whose return\n      value is ignored.\n\n  To use, first, associate `:effect2` with a handler:\n\n      (reg-fx\n         :effect2\n         (fn [value]\n            ... do something side-effect-y))\n\n  Then, later, if an event handler were to return this effects map:\n\n      {:effect2  [1 2]}\n\n  then the `handler` `fn` we registered previously, using `reg-fx`, will be\n  called with an argument of `[1 2]`.\n  "],"~$trim-v",["^ ","^5",["^ ","^6","re_frame/core.cljc","^7",638,"^8",6,"^9",638,"^:",12],"^G","^2U","^6","re_frame/core.cljc","^:",12,"^8",1,"^7",638,"^9",638,"^78","^7@","^6[","An interceptor which removes the first element of the event vector,\n  before it is supplied to the event handler, allowing you to write more\n   aesthetically pleasing event handlers. No leading underscore on the event-v!\n\n  Your event handlers will look like this:\n\n      (reg-event-db\n        :event-id\n        [... trim-v ...]    ;; <-- added to the interceptors\n        (fn [db [x y z]]    ;; <-- instead of [_ x y z]\n          ...)\n    "],"~$clear-sub",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",269,"^8",7,"^9",269,"^:",16,"^6W",["^1G",["^6X",["^1G",[[],["^7B"]]]]],"^6[","Unregisters subscription handlers (presumably registered previously via the use of `reg-sub`). \n   \n  When called with no args, it will unregister all currently registered subscription handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  subscription handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\n\n  NOTE: Depending on the usecase, it may be necessary to call `clear-subscription-cache!` afterwards","^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7B"]],"^6W",["^1G",[[],["^7B"]]],"^75",["^1G",[null,null]]]],"^G","^24","^6","re_frame/core.cljc","^:",16,"^70",["^ ","^71",false,"^72",1,"^73",1,"^74",[[],["^7B"]],"^6W",["^1G",[[],["^7B"]]],"^75",["^1G",[null,null]]],"^74",[[],["^7B"]],"^76",null,"^72",1,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",0,"^71",false,"^78",["^F",[null,"^79"]]],["^ ","^72",1,"^71",false,"^78",["^F",[null,"^79"]]]],"^7",269,"^9",269,"^73",1,"^7;",true,"^6W",["^1G",[[],["^7B"]]],"^6[","Unregisters subscription handlers (presumably registered previously via the use of `reg-sub`). \n   \n  When called with no args, it will unregister all currently registered subscription handlers. \n   \n  When given one arg, assumed to be the `id` of a previously registered \n  subscription handler, it will unregister the associated handler. Will produce a warning to \n  console if it finds no matching registration.\n\n  NOTE: Depending on the usecase, it may be necessary to call `clear-subscription-cache!` afterwards"],"~$dispatch",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",23,"^8",7,"^9",23,"^:",15,"^6W",["^1G",["^6X",["^1G",[["^81"]]]]],"^6[","Queue `event` for processing (handling). \n\n  `event` is a vector and the first element is typically a keyword\n  which identifies the kind of event.\n\n  The event will be added to a FIFO processing queue, so event\n  handling does not happen immediately. It will happen 'very soon'\n  bit not now. And if the queue already contains events, they\n  will be processed first.\n\n  Usage:\n      \n      (dispatch [:order \"pizza\" {:supreme 2 :meatlovers 1 :veg 1}])\n  "],"^G","^2>","^6","re_frame/core.cljc","^:",15,"^74",["^1G",[["^81"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",23,"^7:","^82","^9",23,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^81"]]]]],"^6[","Queue `event` for processing (handling). \n\n  `event` is a vector and the first element is typically a keyword\n  which identifies the kind of event.\n\n  The event will be added to a FIFO processing queue, so event\n  handling does not happen immediately. It will happen 'very soon'\n  bit not now. And if the queue already contains events, they\n  will be processed first.\n\n  Usage:\n      \n      (dispatch [:order \"pizza\" {:supreme 2 :meatlovers 1 :veg 1}])\n  "],"^87",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",653,"^8",7,"^9",653,"^:",12,"^6W",["^1G",["^6X",["^1G",[["~$f"]]]]],"^6[","Returns an interceptor which runs the given function `f` in the `:after`\n  position, presumably for side effects.\n\n  `f` is called with two arguments: the `:effects` value for `:db`\n  (or the `:coeffect` value of `:db` if no `:db` effect is returned) and the event.\n  Its return value is ignored, so `f` can only side-effect.\n\n  An example of use can be seen in the re-frame github repo in `/examples/todomvc/events.cljs`:\n\n     - `f` runs schema validation (reporting any errors found).\n     - `f` writes to localstorage."],"^G","^43","^6","re_frame/core.cljc","^:",12,"^74",["^1G",[["~$f"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",653,"^7:","^7@","^9",653,"^73",1,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["~$f"]]]]],"^6[","Returns an interceptor which runs the given function `f` in the `:after`\n  position, presumably for side effects.\n\n  `f` is called with two arguments: the `:effects` value for `:db`\n  (or the `:coeffect` value of `:db` if no `:db` effect is returned) and the event.\n  Its return value is ignored, so `f` can only side-effect.\n\n  An example of use can be seen in the re-frame github repo in `/examples/todomvc/events.cljs`:\n\n     - `f` runs schema validation (reporting any errors found).\n     - `f` writes to localstorage."],"~$add-post-event-callback",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",900,"^8",7,"^9",900,"^:",30,"^6W",["^1G",["^6X",["^1G",[["~$f"],["^7Q","~$f"]]]]],"^6[","Registers the given function `f` to be called after each event is processed. \n   \n   `f` will be called with two arguments:\n\n    - `event`: a vector. The event just processed.\n    - `queue`: a PersistentQueue, possibly empty, of events yet to be processed.\n\n   This facility is useful in advanced cases like:\n\n     - you are implementing a complex bootstrap pipeline\n     - you want to create your own handling infrastructure, with perhaps multiple\n       handlers for the one event, etc.  Hook in here.\n     - libraries providing 'isomorphic javascript' rendering on  Nodejs or Nashorn.\n\n  `id` is typically a keyword. If it supplied when an `f` is added, it can be \n  subsequently be used to identify it for removal. See `remove-post-event-callback`.\n  ","^70",["^ ","^71",false,"^72",2,"^73",2,"^74",[["~$f"],["^7Q","~$f"]],"^6W",["^1G",[["~$f"],["^7Q","~$f"]]],"^75",["^1G",[null,null]]]],"^G","^20","^6","re_frame/core.cljc","^:",30,"^70",["^ ","^71",false,"^72",2,"^73",2,"^74",[["~$f"],["^7Q","~$f"]],"^6W",["^1G",[["~$f"],["^7Q","~$f"]]],"^75",["^1G",[null,null]]],"^74",[["~$f"],["^7Q","~$f"]],"^76",null,"^72",2,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",1,"^71",false,"^78","^79"],["^ ","^72",2,"^71",false,"^78","^79"]],"^7",900,"^9",900,"^73",2,"^7;",true,"^6W",["^1G",[["~$f"],["^7Q","~$f"]]],"^6[","Registers the given function `f` to be called after each event is processed. \n   \n   `f` will be called with two arguments:\n\n    - `event`: a vector. The event just processed.\n    - `queue`: a PersistentQueue, possibly empty, of events yet to be processed.\n\n   This facility is useful in advanced cases like:\n\n     - you are implementing a complex bootstrap pipeline\n     - you want to create your own handling infrastructure, with perhaps multiple\n       handlers for the one event, etc.  Hook in here.\n     - libraries providing 'isomorphic javascript' rendering on  Nodejs or Nashorn.\n\n  `id` is typically a keyword. If it supplied when an `f` is added, it can be \n  subsequently be used to identify it for removal. See `remove-post-event-callback`.\n  "],"~$reg-cofx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",348,"^8",7,"^9",348,"^:",15,"^6W",["^1G",["^6X",["^1G",[["^7Q","^7Z"]]]]],"^6[","Register the given coeffect `handler` for the given `id`, for later use\n  within `inject-cofx`:\n\n    - `id` is keyword, often namespaced.\n    - `handler` is a function which takes either one or two arguements, the first of which is\n       always `coeffects` and which returns an updated `coeffects`.\n\n  See also: `inject-cofx` \n  "],"^G","^3T","^6","re_frame/core.cljc","^:",15,"^74",["^1G",[["^7Q","^7Z"]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",348,"^7:","^79","^9",348,"^73",2,"^7;",true,"^6W",["^1G",["^6X",["^1G",[["^7Q","^7Z"]]]]],"^6[","Register the given coeffect `handler` for the given `id`, for later use\n  within `inject-cofx`:\n\n    - `id` is keyword, often namespaced.\n    - `handler` is a function which takes either one or two arguements, the first of which is\n       always `coeffects` and which returns an updated `coeffects`.\n\n  See also: `inject-cofx` \n  "],"~$reg-event-fx",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",468,"^8",7,"^9",468,"^:",19,"^6W",["^1G",["^6X",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]]]],"^6[","Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n\n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (coeffects-map event-vector) -> effects-map\n    - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n\n\n  Example Usage:\n\n      (reg-event-fx \n        :token \n        (fn [cofx event]\n          {:db (assoc (:db cofx) :some-key (get event 2))}))   ;; return a map of effects\n\n\n  Or perhaps:\n\n      (reg-event-fx\n        :namespaced/id           ;; <-- namespaced keywords are often used\n        [one two three]          ;; <-- a seq of interceptors\n        (fn [{:keys [db] :as cofx} [_ arg1 arg2]] ;; destructure both arguments\n          {:db       (assoc db :some-key arg1)          ;; return a map of effects\n           :dispatch [:some-event arg2]}))\n  ","^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^75",["^1G",[null,null]]]],"^G","^37","^6","re_frame/core.cljc","^:",19,"^70",["^ ","^71",false,"^72",3,"^73",3,"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^75",["^1G",[null,null]]],"^74",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]],"^76",null,"^72",3,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^77",[["^ ","^72",2,"^71",false,"^78","^79"],["^ ","^72",3,"^71",false,"^78","^79"]],"^7",468,"^9",468,"^73",3,"^7;",true,"^6W",["^1G",[["^7Q","^7Z"],["^7Q","^7[","^7Z"]]],"^6[","Register the given event `handler` (function) for the given `id`. Optionally, provide\n  an `interceptors` chain:\n\n    - `id` is typically a namespaced keyword  (but can be anything)\n    - `handler` is a function: (coeffects-map event-vector) -> effects-map\n    - `interceptors` is a collection of interceptors. Will be flattened and nils removed.\n\n\n  Example Usage:\n\n      (reg-event-fx \n        :token \n        (fn [cofx event]\n          {:db (assoc (:db cofx) :some-key (get event 2))}))   ;; return a map of effects\n\n\n  Or perhaps:\n\n      (reg-event-fx\n        :namespaced/id           ;; <-- namespaced keywords are often used\n        [one two three]          ;; <-- a seq of interceptors\n        (fn [{:keys [db] :as cofx} [_ arg1 arg2]] ;; destructure both arguments\n          {:db       (assoc db :some-key arg1)          ;; return a map of effects\n           :dispatch [:some-event arg2]}))\n  "],"~$register-handler",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^:",23,"^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",["^6Z"]]],"^6W",["^1G",[["~$&","^6Z"]]],"^75",["^1G",[null]]],"^8",7,"^7",934,"^7N","0.8.0","^9",934,"^6W",["^1G",["^6X",["^1G",[["~$&","^6Z"]]]]],"^6[","Deprecated. Use `reg-event-db` instead."],"^G","^3?","^6","re_frame/core.cljc","^:",23,"^70",["^ ","^71",true,"^72",0,"^73",0,"^74",[["^1G",["^6Z"]]],"^6W",["^1G",[["~$&","^6Z"]]],"^75",["^1G",[null]]],"^74",[["^1G",["^6Z"]]],"^76",null,"^72",0,"^75",["^1G",[null]],"^8",1,"^71",true,"^77",[["^ ","^72",0,"^71",true,"^78","^79"]],"^7",934,"^7N","0.8.0","^7:","^79","^9",934,"^73",0,"^7;",true,"^6W",["^1G",[["~$&","^6Z"]]],"^6[","Deprecated. Use `reg-event-db` instead."],"~$clear-subscription-cache!",["^ ","^6V",null,"^5",["^ ","^6","re_frame/core.cljc","^7",285,"^8",7,"^9",285,"^:",32,"^6W",["^1G",["^6X",["^1G",[[]]]]],"^6[","Removes all subscriptions from the cache.\n\n  This function can be used at development time or test time. Useful when hot realoding\n  namespaces containing subscription handlers. Also call it after a React/render exception,\n  because React components won't have been cleaned up properly. And this, in turn, means \n  the subscriptions within those components won't have been cleaned up correctly. So this \n  forces the issue.\n  "],"^G","^3J","^6","re_frame/core.cljc","^:",32,"^74",["^1G",[[]]],"^76",null,"^75",["^1G",[null,null]],"^8",1,"^71",false,"^7",285,"^7:",["^F",["^79","^82"]],"^9",285,"^73",0,"^7;",true,"^6W",["^1G",["^6X",["^1G",[[]]]]],"^6[","Removes all subscriptions from the cache.\n\n  This function can be used at development time or test time. Useful when hot realoding\n  namespaces containing subscription handlers. Also call it after a React/render exception,\n  because React components won't have been cleaned up properly. And this, in turn, means \n  the subscriptions within those components won't have been cleaned up correctly. So this \n  forces the issue.\n  "]],"^1E",["^ ","^10","^10"],"~:cljs.analyzer/constants",["^ ","^1?",["^F",["~:warn","~:after","~:id","~:before"]],"~:order",["^8N","^8O","^8M","^8L"]],"^1K",["^ ","^1@",["^F",[]]],"^1L",["^ "],"^1M",["^12","^10","^W","^O","^M","^16","^V","^S","^14","^Z","^Y","^[","^T","^1;","^18","^Q"]],"^J","^H","~:ns-specs",["^ "],"~:ns-spec-vars",["^F",[]],"~:compiler-options",["^45",[["^8S","~:static-fns"],true,["^8S","~:shadow-tweaks"],null,["^8S","~:source-map-inline"],null,["^8S","~:elide-asserts"],false,["^8S","~:optimize-constants"],null,["^8S","^1R"],null,["^8S","~:external-config"],null,["^8S","~:tooling-config"],null,["^8S","~:emit-constants"],null,["^8S","~:load-tests"],null,["^8S","~:form-size-threshold"],null,["^8S","~:data-readers"],null,["^8S","~:infer-externs"],"~:auto",["^8S","^1T"],null,["~:js-options","~:js-provider"],"^1@",["~:mode"],"~:dev",["^8S","~:fn-invoke-direct"],null,["^8S","~:source-map"],"/dev/null"]]]