This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-21
Channels
- # aws (2)
- # bangalore-clj (1)
- # beginners (25)
- # boot (2)
- # cider (176)
- # clara (73)
- # cljs-dev (6)
- # cljsrn (31)
- # clojure (40)
- # clojure-greece (9)
- # clojure-india (1)
- # clojure-italy (14)
- # clojure-nl (9)
- # clojure-russia (4)
- # clojure-uk (156)
- # clojurescript (124)
- # core-async (37)
- # cursive (2)
- # data-science (2)
- # datomic (22)
- # emacs (3)
- # fulcro (32)
- # graphql (6)
- # java (3)
- # lein-figwheel (19)
- # lumo (29)
- # nyc (1)
- # off-topic (9)
- # onyx (15)
- # portkey (12)
- # precept (2)
- # re-frame (15)
- # reagent (10)
- # rum (7)
- # schema (2)
- # shadow-cljs (48)
- # tools-deps (35)
- # yada (1)
Are there any docs/blog posts/resources for how to do authentication/authorization with lacinia?
I'll eventually work up to that in the tutorial. It's really more Pedestal-based than Lacinia-based.
@madstap An option is to use a pedestal interceptor and use that from the context when needed I believe. Haven't tried it myself yet.
So something like passing in a token via interceptor and in every resolver read that out of the context map?
Somewhat related, I have been following the tutorial here http://lacinia.readthedocs.io/en/latest/tutorial/index.html
In it every resolver function calls out to the database when called. since I'm using datomic it would be nice if every part of a query had a stable view of the database. Would it be reasonable to pass a datomic database value in the context as well? Or passing just the t
value would be better?