This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-06-30
Channels
- # admin-announcements (19)
- # announcements (4)
- # beginners (22)
- # boot (76)
- # cider (92)
- # clojure (235)
- # clojure-berlin (3)
- # clojure-germany (1)
- # clojure-italy (8)
- # clojure-japan (18)
- # clojure-russia (26)
- # clojure-sg (1)
- # clojure-uk (25)
- # clojurescript (55)
- # code-reviews (7)
- # core-async (53)
- # datomic (13)
- # euroclojure (63)
- # jobs (39)
- # ldnclj (45)
- # off-topic (9)
- # om (7)
- # onyx (6)
- # reading-clojure (1)
- # reagent (5)
- # yada (22)
@dnolen: Woke up to see Replete is the #1 top trending Swift GitHub repo. Go bootstrapped ClojureScript and thanks community! https://github.com/trending?l=swift
Hi, I'm using Om and trying to fetch some data from the server. I have a component that needs this data has no access to it. I tried to use ref-cursors but failed because I can't observe a path in the app-state that is not yet there. Did anyone have a similar problem?
I tried to do an om/update!
with an empty hashmap right before om/observe
but that doesn't work because the update is still in the queue when I call om/observe
Hi all, I'm getting warmed up with the ideas around @dnolen's talk at EuroClojure and was wondering if anyone had been giving any thoughts wrt the update path for entities. @dnolen referred to it as a topic not adressed yet, is there a particular place to follow developments around this ?
@tcrayford: alright, much clearer. the formalism around optimistic mutation is really interesting
and indeed, you'd see how om components could end up having mutate!
functionality to perform these
in case anyone is interested: I have just managed to run cljs on Node.js on a Linux PowerPC box using the IBM Node.js DSK for PowerPC.
so according to the material in the above presentation, in addition to query-params
and queries
a component could end up having mutations
except for the fact that building the query endpoint for non-datomic backed apps will be a bit painful
(yeller for example, could implement this pretty easily, and it's just using riak on the backend)
@tcrayford: agreed, and anyhow, it does end up being simpler than wrapping every entity access behind a REST entity
becomes a pre-query "can the user actually make this query" thing or a post query "hide fields they aren't allowed to see"
@samueldev: In Om you have access to all lifecycle functions you have in React
I have a very hairy function with many nested functions which shadow some of the fn locals
and I got a few errors like this one: ERROR - Parse error. Duplicate parameter name "params__$1"
is anybody attending React Europe this week? would be happy to meet fellow clojurians
@txus most likely the result of a bad macro in a library your are using, not a ClojureScript bug.
I've got a dumb question about the clojurescript build api. The following throws a parse error and returns back incorrect javascript: (cljs.build.api/build '((ns test.test) (+ 1 1)) {:optimizations :advanced})
. I have no idea why or what I am doing wrong. It looks like anytime a var is defined with ns or def a parse error gets thrown? Very puzzled and unsure how to debug this.
Figured it out (I hope). It looks like there is a difference between passing in '((ns test.test) (+ 1 1))
and '[(ns test.test) (+ 1 1)]
.
I can only guess at the reason, since both lists and vectors extend have the compilable protocol extended for them.
I’m buying some books from The Pragmatic Bookshelf and PACKT. Any books I should buy that could help with building one page mobile friendly web apps?
Is it worth reading a book on ReactJS?
i suspect reactjs wouldn't fill more than a chapter or two -- flux would probably be the more useful book, but not sure any exist
What’s flux?
it's an architecture for building applications with react -- basically, it tries to fill in the gaps on how to do the "not rendering" stuff in an application with react -- https://github.com/facebook/flux
Are Reagent and Om built on top of flux?