@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)