This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-03
Channels
- # bangalore-clj (1)
- # beginners (160)
- # boot (174)
- # cider (57)
- # cljs-dev (16)
- # cljsrn (5)
- # clojure (144)
- # clojure-argentina (1)
- # clojure-austin (6)
- # clojure-finland (2)
- # clojure-france (4)
- # clojure-russia (185)
- # clojure-serbia (4)
- # clojure-spec (61)
- # clojure-uk (126)
- # clojurescript (212)
- # community-development (7)
- # core-async (2)
- # cursive (17)
- # datomic (210)
- # emacs (10)
- # euroclojure (2)
- # gsoc (23)
- # hoplon (86)
- # jobs (8)
- # lein-figwheel (9)
- # luminus (19)
- # lumo (12)
- # off-topic (4)
- # om (14)
- # om-next (6)
- # pedestal (38)
- # perun (11)
- # planck (35)
- # portland-or (2)
- # ring (1)
- # ring-swagger (28)
- # specter (6)
- # untangled (6)
- # yada (2)
Blueprintjs bindings for Om/OmNext: https://github.com/drcode/blueprint-cljs
Look at how small/clean the source code is for the demo: https://github.com/drcode/blueprint-cljs/blob/master/examples/kitchensink/src/kitchensink/core.cljs
In my opinion, Palantir's Blueprintjs is a perfect companion for Om/OmNext: It gives us a boatload of high quality components with a minimal overhead. I hope the community will give it closer a look!
@danvingo be sure to read the caveats at the end of the README.md (lt;dr: still very alpha)
hello guys, newbie question for om.next
I don’t understand why the the read
function received :parser
& :query
in the env
(it’s obvious why :state
is passed)
If a query is nested (as most queries are) then Om Next will not parse the child query automatically, by design. Instead, you either have to call db->tree (if your state is normalized and you don't care about possibly sending extraneous information) our you need to call ((:parser env) env (:query env))
yes, i've found the solution in @tony.kay github tuto
i still struggle a little but it's a lot of fun :-)