Fork me on GitHub
#re-frame
<
2017-10-07
>
lovuikeng08:10:05

thank you @danielcompton, great tops on the polling-interval effect on the FAQ https://github.com/Day8/re-frame/blob/master/docs/FAQs/PollADatabaseEvery60.md Noticed also CQRS backend is recommended for re-frame https://github.com/Day8/re-frame/blob/master/docs/FAQs/FullStackReframe.md, is it because it matches better with the even-driven nature of re-frame itself?

danielcompton16:10:22

Not my docs sorry, I think they’re Mike’s?

lovuikeng17:10:38

database polling effect. thought you wrote that one?

jvuillermet10:10:47

Reading at the FAQ about clear-subscription-cache! , I’m wondering if the new error boundaries on React 16 -when Reagent eventually take advantage of it- will allow re-frame to dispose correctly ?

Jon10:10:20

An early prototype. More at https://github.com/Respo/reel . I'm wondering if re-frame does that?

mikethompson11:10:25

@jiyinyiyong in addition to re-frisk ... there's also re-frame-undo and re-frame-trace which are related. The later is still under development

lovuikeng11:10:46

@mikethompson will re-frame-trace will available as profile in re-frame-template?

mikethompson11:10:31

@lovuikeng once it gets more solid, yes

mikethompson11:10:45

But there's still a bit to do

Jon11:10:43

😛 I prefer my own solution since I don't use React, thus mine can be simpler

Jon11:10:15

I don't have a beautiful devtools for Respo though.

lovuikeng11:10:20

Both respo and reel don't seem to be related to re-frame except for the look 'n feel

Jon13:10:11

Respo is my own virtual DOM lib. I'm not really into Reagent and barely used re-frame. I just think the ideas behind use are similar. And we both get ideas from Elm and Redux.

dfcarpenter20:10:26

This is a beginner question. I'm looking at the braid repository ( a chat app in clj/cljs using re-frame) and im curious about a small detail about events. I cant find out how this syntax works https://github.com/braidchat/braid/blob/master/src/braid/client/gateway/helper_views.cljs#L13

dfcarpenter20:10:30

specifically the

(on-change-transform (.. e -target -value))
for property access.

rgm20:10:29

I think (.. e -target -value) is equivalent to the threading macro (-> e .-target .-value), which unrolled would be (.-value (.-target e))

rgm20:10:47

but (.. whatever) is only in JS.

rgm20:10:08

(js equivalent would be, of course, good 'ol e.target.value)

rgm20:10:47

without the dash it gets interpreted into JS as e.target().value(), ie. chained method calls.

jeaye21:10:41

I'd strongly recommend against not using that notation though.

jeaye21:10:59

It doesn't work well with :advanced optimization at all.

jeaye21:10:31

Instead, do all member access using https://github.com/binaryage/cljs-oops