om

Please ask the channel first, not @dnolen directly!
gmercer 2017-06-14T10:05:11.819488Z

@ssaul simply bump the version from 1.9.542 (as it is in the repo) to 1.9.562 the examples will compile - NB you must clear your caches in your browser

gmercer 2017-06-14T10:07:23.851391Z

if someone here has commit rights they could bump this version and your pain would go away - can one of the committers do a fresh clone and run the hello example ??

ssaul 2017-06-14T13:45:04.216892Z

That is why I wanted to know if anyone actually got the example (or any of the examples) to work.

ssaul 2017-06-14T13:55:53.471717Z

Oh yeah, it compiled with warnings.

lein cljsbuild once hello
Compiling ClojureScript...
Compiling "examples/hello/main.js" from ["src" "examples/hello/src"]...
WARNING: Use of undeclared Var cljs.pprint/pprint at line 15 examples/hello/out/devcards/util/utils.cljs
WARNING: Use of undeclared Var cljs.pprint/with-pprint-dispatch at line 23 examples/hello/out/devcards/util/utils.cljs
WARNING: Use of undeclared Var cljs.pprint/code-dispatch at line 23 examples/hello/out/devcards/util/utils.cljs
WARNING: Wrong number of args (1) passed to UUID at line 564 examples/hello/out/cljs/reader.cljs
WARNING: Use of undeclared Var clojure.string/starts-with? at line 822 examples/hello/out/cljs/analyzer.cljc
WARNING: Use of undeclared Var clojure.string/ends-with? at line 972 examples/hello/out/cljs/analyzer.cljc
WARNING: Use of undeclared Var clojure.string/starts-with? at line 2643 examples/hello/out/cljs/analyzer.cljc
WARNING: Can't take value of macro cljs.core/require at line 15 examples/hello/out/cljs/nodejs.cljs
WARNING: require already refers to: cljs.core/require being replaced by: cljs.nodejs/require at line 15 examples/hello/out/cljs/nodejs.cljs
Successfully compiled "examples/hello/main.js" in 22.095 seconds.
Not sure if that matters to much but just putting it out there incase there is some solution issue tied to any of these warnings.

dnolen 2017-06-14T17:07:49.304635Z

@anmonteiro still have issues with the README? Thinking about merging this in

anmonteiro 2017-06-14T17:14:27.453076Z

@dnolen I’ll look into it in 5

dnolen 2017-06-14T17:19:02.554905Z

thanks

anmonteiro 2017-06-14T18:07:15.675554Z

@dnolen looks good now

dnolen 2017-06-14T18:10:47.756926Z

cool!

gmercer 2017-06-14T20:54:25.308243Z

@ssaul I got the same error it ended up being a cached version of devtools, hence the note about clearing the cache - I tried in four other browsers (where I rarely use clojurescript) and they worked, went back to chrome with a hard reload and Bob's your uncle

ssaul 2017-06-14T20:56:39.354983Z

oh ok. I cleared my cache (at least I thought I did). Will try it again. Thanks you so much.

gmercer 2017-06-14T20:58:30.393374Z

or different browser? time to try Brave browser (debugging is less fun as the inspector is not dockable, yet)

ssaul 2017-06-14T20:59:50.421416Z

i tried it in another browser, (safari) and got the same error. I think I will blow away my local om repo, clear my cache, and restart my computer. At this point, I am pretty sure it has to be something I am doing wrong or something with my environment.

gmercer 2017-06-14T21:03:30.498827Z

yeah - I tied absolutely fresh clone then bump version then compile

ag 2017-06-14T21:14:02.698714Z

can someone help me with the correct quoting I need to include mutation key in the query, something like this:

(defui Comp
  static om/IQuery
  (query [_] ['foo/create!]))
why? because when I use :remote true in mutate method, it sends it to the server, there result of operation comes back in {:value result}, as novelty it gets stored in the state under 'foo/create! key. Now I need to read it. Can't figure out proper way to quote it

ag 2017-06-14T21:18:18.776363Z

I can create intermediate key e.g. :create-result and do it in corresponding read method, but why can't I just grab it directly?

dnolen 2017-06-14T22:53:41.161187Z

@ag because mutations can change anything they want

dnolen 2017-06-14T22:53:57.164203Z

you can’t possibly know which keys are affected

dnolen 2017-06-14T22:54:36.171727Z

I mean if you’re in total control of client/server sure - but in general you cannot

dnolen 2017-06-14T22:54:46.173476Z

so we made the same tradeoff that Falcor/Relay did here

ag 2017-06-14T22:58:07.210951Z

got it. I am now still returning result of remote mutation which as novelty gets attached to the state with the key .e.g: 'foo/create!, but I'm using a different key e.g: :foo/create-result and read method to read that