This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-19
Channels
- # aws (9)
- # bangalore-clj (1)
- # beginners (6)
- # cider (17)
- # cljs-dev (9)
- # cljsrn (31)
- # clojure (70)
- # clojure-spec (19)
- # clojurescript (122)
- # cursive (1)
- # datomic (20)
- # dirac (8)
- # fulcro (19)
- # hoplon (25)
- # instaparse (2)
- # lambdaisland (3)
- # luminus (8)
- # lumo (10)
- # om (22)
- # parinfer (25)
- # protorepl (2)
- # re-frame (35)
- # reagent (1)
- # test-check (5)
- # unrepl (6)
@mikethompson from your answer above what is a level 1 subscription? Would that be a static value. Coulndt find it in the graphic
Anyone remember the handle of the gentleman who wrote re-frisk? I think he changed it and I can't think to what
@lumpy See my notes above for "Level 1"
And see the infographic. Described in both places. But I do mix the terms "Level 1" and "Layer 1"
also if anyone has any ideas about tracking down "re-frame: expected a vector, but got: null" followed by "re-frame: no subscription handler registered for: '', Returning a nil subscription". Neither appear to touch any of my app code.
seems to be going on somewhere in the re-frisk setup code but i've no idea why it's started to happen
@sandbags I'd guess that means there's a (subscribe)
somewhere?
Ie. no vector provided as an arg
@mikethompson right, just not sure why that should suddenly be true for re-frisk
Layer 1 entire app-db, Layer 2 portions of app-db, Layer 3 multiple portions of app-db combined together. is that the gist of it?
Layer 1 - app-db
Layer 2 - extractors
Layer 3 - derived values (from extracted values)
Layer 3 sometimes involves time-consuming computation
the only change i think i made was adding re-frame-datatable
perhaps there is some incompatibility
I'd put a breakpoint in the re-frame itself, at the line of code which produces the error message and have a look at the call stack. Or perhaps you already have ... and that's how you narrowed down to re-frisk?
motor4ik
That's the handle of Mr re-frisk .... or at least it used to be ... I think
Ahh, snap
ok i see the errant subscribe
but i'm not sure why it's broken. Presumably re-frisk
is fishing around in kind->id->handler
before its fully formed