This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-16
Channels
- # beginners (11)
- # boot (21)
- # cider (12)
- # clara (6)
- # cljs-dev (7)
- # cljsjs (1)
- # cljsrn (62)
- # clojure (137)
- # clojure-austin (5)
- # clojure-italy (1)
- # clojure-nl (2)
- # clojure-russia (46)
- # clojure-spec (21)
- # clojure-uk (79)
- # clojurescript (56)
- # clr (1)
- # core-typed (1)
- # css (1)
- # cursive (3)
- # datomic (35)
- # docker (2)
- # emacs (20)
- # garden (3)
- # hoplon (8)
- # incanter (3)
- # jobs (12)
- # mount (5)
- # nginx (1)
- # off-topic (71)
- # om (8)
- # om-next (6)
- # onyx (4)
- # perun (3)
- # proton (2)
- # protorepl (5)
- # re-frame (35)
- # reagent (38)
- # ring (5)
- # ring-swagger (12)
- # rum (35)
- # spacemacs (2)
- # specter (5)
- # test-check (6)
- # yada (52)
Maybe someone can illuminate why every component but the root component must be passed to (om/factory) before it grabs onto the screen? Does (om/add-root!) implicitly do this step?
@stijn https://github.com/danielsz/system-websockets/blob/master/src/cljs/demo/core.cljs#L136
Lines 136, 137, 138 show how one could use a case statement to adjust what renders based on authenticated session or not. However, I think you were wondering about not sending data over the wire, not just not rendering/displaying it.. Hmm.. Maybe you can match every query word against a permission level... serverside parser ... :remote
@stijn excellent find. the (owns?) is still blurry to me on first glance because it looks like you need two ...(owner-rules) and (owns?) but I can sorta feel the gist.