This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-19
Channels
- # aws-lambda (1)
- # bangalore-clj (4)
- # beginners (66)
- # boot (13)
- # cider (9)
- # cljs-dev (44)
- # cljsjs (3)
- # clojure (181)
- # clojure-austin (2)
- # clojure-greece (6)
- # clojure-italy (2)
- # clojure-russia (64)
- # clojure-sg (1)
- # clojure-spec (68)
- # clojure-uk (60)
- # clojurescript (66)
- # conf-proposals (12)
- # cryogen (1)
- # cursive (3)
- # datomic (44)
- # graphql (1)
- # hoplon (2)
- # jobs (2)
- # jobs-discuss (3)
- # keechma (2)
- # liberator (6)
- # luminus (2)
- # nyc (1)
- # off-topic (92)
- # om (10)
- # onyx (17)
- # parinfer (39)
- # pedestal (8)
- # proton (11)
- # re-frame (110)
- # reagent (2)
- # remote-jobs (11)
- # ring-swagger (9)
- # rum (2)
- # sql (2)
- # test-check (6)
- # untangled (138)
Any reason why I would not see a UUID printed in the console when using om/transact! ?
@kardan I've seen it's hidden in later versions of Chrome. Try adjusting your log filters.
I no longer see it under 'Info', I have to change to 'Verbose'
I'm not sure why because I believe the log level should be info.
Question about om-next / Datomic interaction. I'm sending my requests from the client over transit+json and I want to leverage Datomic's pull syntax. I have this working when I define all the parameters I want, but I am having difficulties using wildcard syntax. Anyone have a suggestion or link to an example if this is possible?
example of what I want to be able to define on the client: (:user/by-id '[* {:user/permissions [*]}])