This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-25
Channels
- # aws (2)
- # aws-lambda (2)
- # beginners (95)
- # boot (47)
- # cider (13)
- # clara (5)
- # cljs-dev (36)
- # cljsjs (9)
- # clojure (51)
- # clojure-austin (1)
- # clojure-greece (25)
- # clojure-italy (4)
- # clojure-japan (10)
- # clojure-russia (13)
- # clojure-spec (61)
- # clojure-uk (25)
- # clojurescript (26)
- # core-matrix (5)
- # cursive (8)
- # data-science (7)
- # datomic (43)
- # dirac (2)
- # emacs (8)
- # events (3)
- # fulcro (17)
- # graphql (29)
- # jobs-rus (4)
- # lambdaisland (4)
- # lein-figwheel (3)
- # leiningen (60)
- # luminus (15)
- # lumo (8)
- # mount (3)
- # off-topic (28)
- # om (22)
- # onyx (115)
- # other-languages (6)
- # pedestal (5)
- # re-frame (41)
- # reagent (12)
- # ring-swagger (12)
- # shadow-cljs (127)
- # unrepl (27)
- # yada (5)
@hlship: Does lacinia-pedestal support configuring CORS out of the box? It seems it doesn’t set the Access-Control-Allow-Origin
header / OPTIONS
request by default.
Use lacinia-pedestal. It ships with graphiql out of the box.
Say, anyone using lacinia with a datomic back-end? It seems doable but I'm not sure what the best way to handle namespaced keys is
I’m using both, pretty awesome together. I just have some functions that handle the namespacing/de-namespacing
Are you trying to preserve the namespaces, like :user/name
-> "user.name"
or something?
I have a few keys like :project.domain/thing.category
that seem a little tricky to deal with
Yeah in this case, i’m building the Datomic db and the GQL stuff together so I kind of just follow a pattern of User.name <-> :user/name
Cool, glad to hear it's workable
Is there one central place where you can hook into the conversion, or are you just wrapping input/output to the API?
Ok, sweet. Thanks for the info, I'll play around with it some
I’d started with something like this
{:common-object-fields {:entity/gid "gid"
:entity/active "active"
:entity/legacy_id "legacyId"}
:objects {
:Person {:description "A Person"
:fields {:person/* :map-name}}
:Program {}}}
but haven’t played with it much more, but the thinking was that say if all the Person fields mapped 1-1 then that wild card would work, but you could also do one offs, etcv
Ah, I think it's because I didn't include attachments. Interesting to see a spec error instead of an arity error.
It'd be nice to be able to parse a schema IDL without specifying the attachments first so that the parsed schema could be used to programmatically build the attachments.