This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-14
Channels
- # beginners (4)
- # boot (78)
- # braveandtrue (3)
- # cider (9)
- # clara (6)
- # cljs-dev (4)
- # clojure (57)
- # clojure-brasil (1)
- # clojure-russia (99)
- # clojure-spec (20)
- # clojure-uk (40)
- # clojurescript (162)
- # component (17)
- # cursive (4)
- # datomic (21)
- # docker (2)
- # emacs (5)
- # figwheel (2)
- # hoplon (363)
- # jobs (1)
- # leiningen (1)
- # om (4)
- # om-next (5)
- # onyx (10)
- # proton (1)
- # re-frame (13)
- # reagent (13)
- # ring (3)
- # rum (1)
- # slack-help (1)
- # test-check (3)
- # untangled (7)
- # vim (24)
Okay my app layout: Backend.clj talks to Datomic and Does Sente Sockets. Frontend.clj has Om.next and an App-state atom. Presumably now I just link Datomic-updates to Sente, merge the new data with the app-state-atom when it's received on the front end and... realtime! am i missing anything?
How would you go about implementing authorization in om.next queries on the backend (like http://graphql.org/learn/authorization/) using datomic?
what i've already found: 1/ filtered db like in https://youtu.be/7lm3K8zVOdY?t=720, 2/ limiting the pull spec you can send in through the query (but that also limits flexibility on the client side)
@stijn that is an excellent question. My first question is how does your om.next talk to your backend?