This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-24
Channels
- # beginners (13)
- # cider (1)
- # cljsrn (2)
- # clojars (5)
- # clojure (110)
- # clojure-czech (1)
- # clojure-dusseldorf (3)
- # clojure-japan (1)
- # clojure-spec (39)
- # clojurescript (13)
- # cloverage (2)
- # cursive (2)
- # defnpodcast (4)
- # lein-figwheel (7)
- # off-topic (1)
- # om (38)
- # om-next (4)
- # perun (1)
- # planck (3)
- # reactive (8)
- # rethinkdb (1)
- # ring-swagger (1)
- # specter (17)
- # vim (1)
- # yada (4)
Just reading om-next considering for a CRM as a SPA. Is normalization an ongoing process? e.g. if server pushes more data to client? Do I even want Om to do normalization when working with a remote store?
@nowprovision That's right: when you merge novel data into the app, the data will be normalized for you (if you have normalization on)
Since it's optional, I'd say play with it, and see if it makes sense for you. It's more solid than you might think.
@peeja FYI currently working on fixing your set-query!
bug
@anmonteiro Ah, that makes sense. Thank you!
this change could eventually lead to dropping some useless code in the monster that is build-index
I just don’t have time to look into that right now
@anmonteiro I had a thought earlier this week: rather than use two mixins to set the query and build a wrapper, why not use the query from the wrapper component?
@peeja because the wrapper component sits between the root component and the component of the current route
there would be no way to compose those queries
I think it does
That's only because the wrapper currently receives the factory and the route's props, and it puts them together
If Compassus built the route component itself and passed the component into the wrapper, it would work
that might work
@peeja I have to look into that, mind opening an issue so I don’t forget?
awesome, thanks!
For development of om itself, should bin/test
always pass? I'm getting a compilation error on a fresh checkout
/Users/grzm/Documents/dev/om-dev/om/target/test/out/om/next/tests.js:696
return cljs.core._conj(cljs.core.Lisreturn cljs.core._conj(clj})(),new cljs.core.Symbol(null,"not","not",1044554643,null)),new cljs.core.Keyword(null,"message","message",-406056002),null], null));
^^^^^^^^^
SyntaxError: missing ) after argument list
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at global.CLOSURE_IMPORT_SCRIPT (/Users/grzm/Documents/dev/om-dev/om/target/test/out/goog/bootstrap/nodejs.js:75:3)
at Object.goog.importScript_ (/Users/grzm/Documents/dev/om-dev/om/target/test/out/goog/base.js:907:9)
at Object.goog.writeScripts_ (/Users/grzm/Documents/dev/om-dev/om/target/test/out/goog/base.js:1420:16)
@grzm weird getting that too
I normally just run boot test
these days
that worked fine. Thanks, @anmonteiro
@grzm hrm, it’s running in CircleCI currently
is there a case to made for Travis?
I wasn't aware it was in CircleCI. Is the current build status available? I guess it's passing boot test
🙂
Nice! Would you accept a pull request to add a build status badge? https://circleci.com/gh/omcljs/om.svg?style=shield&circle-token=:circle-token
I think there’s already one