This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-22
Channels
- # admin-announcements (7)
- # beginners (56)
- # boot (69)
- # cider (168)
- # cljs-dev (2)
- # clojure (170)
- # clojure-austin (25)
- # clojure-beijing (3)
- # clojure-belgium (2)
- # clojure-france (3)
- # clojure-poland (17)
- # clojure-russia (115)
- # clojure-uk (40)
- # clojurebridge (3)
- # clojurescript (87)
- # cursive (9)
- # datomic (30)
- # dirac (18)
- # editors (3)
- # emacs (14)
- # hoplon (195)
- # immutant (14)
- # jobs (3)
- # jobs-discuss (4)
- # leiningen (11)
- # melbourne (5)
- # mount (42)
- # off-topic (5)
- # om (24)
- # onyx (48)
- # parinfer (53)
- # proton (1)
- # protorepl (2)
- # re-frame (3)
- # reactive (2)
- # reagent (29)
- # rum (5)
- # spacemacs (4)
- # untangled (91)
- # yada (1)
@mikethompson: I see why a macro might be handy here. Putting the trace into the event would allow middleware to show/ignore and also I guess in an error case the trace could be used to provide a better stacktrace
@cork: GraphQL is just a query language, you could use GraphQL in lieu of making a REST endpoint call. What you are referring to with components being hooked up directly to the data source is called Relay I think, which is a thing built on top of GraphQL.
hey @mikethompson I bumped into exactly the issue you described https://github.com/mike-thompson-day8/cljsbuild-none-test-seed with optimizations :none
… i’m wondering if this is still applicable, or if you found another way around the issue? (repos is a year old)