This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-06
Channels
- # alda (3)
- # beginners (109)
- # boot (24)
- # cljsrn (17)
- # clojure (41)
- # clojure-brasil (2)
- # clojure-china (1)
- # clojure-russia (19)
- # clojure-spec (9)
- # clojure-uk (5)
- # clojurescript (44)
- # cloverage (5)
- # core-async (3)
- # css (2)
- # datascript (6)
- # datomic (26)
- # emacs (2)
- # events (10)
- # hoplon (24)
- # lambdaisland (1)
- # om (2)
- # onyx (16)
- # other-languages (10)
- # proto-repl (2)
- # re-frame (14)
- # spacemacs (2)
- # untangled (4)
- # videos (1)
@escherize: wewt, thanks, onBlur
is a hack I can live with! I just have to avoid setting the <input>’s :value
, and just replace onChange
with onBlur
. Will look forward to unexpected user-reported bugs from that 😛
@shader: per the re-frame doc, r-atom
is really a signal
i.e., a value that changes over time, i.e., a stream.
From a ClojureScript perspective, the purpose of an atom is to hold mutable data. From a re-frame perspective, we'll tweak that paradigm slightly and view a ratom as having a value that changes over time.
So, in FRP-ish terms, a reaction will produce a "stream" of values over time (it is a Signal), accessible via the ratom it returns.
[And, having used Elm, I can say that although specifics are slightly different the end result in terms of syntax is quite similar and in terms of mechanics almost identical].
@johnatan you haven't given us much to work with. But this general answer might help you: http://stackoverflow.com/a/37186230/5215391
I’ve used this template, but I often get an error:
history.js:907 Uncaught TypeError: Cannot set property 'value' of null
goog.History.update_ @ history.js:907
goog.History.onHashChange_ @ history.js:598
goog.events.fireListener @ events.js:728
goog.events.handleBrowserEvent_ @ events.js:852
(anonymous function) @ events.js:277
@mnewhook: please also open an issue on github so it doesn't get lost on slack :)
@mikethompson: nope, that really doesn't help much. My situation is this: a v-box
with N h-boxes
inside. I put a valid/meaningful key on the h-boxes
like so: ^{:key the-key}
and yet when I examine the data-react-ids
for the h-boxes
, they do not have my key component.
@mikethompson: I was reading https://github.com/Day8/re-frame/wiki/Effectful-Event-Handlers#order-of-effects and you state that you would need to return a vector of maps in case order handling is necessary. Am I completely off in saying that you could use array-map
in order to seq
on the kv preserving the insertion order? Of course then your map cannot be that big (lookup is linear) but I don't see it growing super big anyways