Fork me on GitHub
#re-frame
<
2016-09-28
>
samueldev14:09:04

Am I understanding correctly that interceptors, in this context: https://github.com/Day8/re-frame/blob/master/examples/todomvc/src/todomvc/events.cljs... todo-interceptors ... wherein the only "part" of the app-db that those handlers have access to is the "todos" portion, is done so to purposely limit the parts of the app-db that any particular handler can modify?

samueldev14:09:33

When my browser auto-fills an input (saved un/pw for example), it isn't triggering the on-change of my component

samueldev14:09:50

seems like this is just known behaviour in many browsers, wondering if there's any good re-frame/reagent workaround

mattly20:09:19

is there a good writeup of how to use signal dependencies with reg-sub under 0.8?

mattly20:09:31

I'm in the middle of updating fro register-sub and there are a few places where I'm using dependent signals and can't figure out how to adapt them

mattly20:09:40

I'm doing similar things to the first example here from the readme: https://github.com/Day8/re-frame#a-more-efficient-signal-graph

rafaelzlisboa20:09:55

@mattly if i understood correctly, you could use something like https://github.com/Day8/re-frame/blob/master/examples/todomvc/src/todomvc/subs.cljs#L130 (after registering each of the dependent reactions as a sub)

mattly21:09:45

eh I had inline reactions instead of first-class subscriptions, similar to the place in the readme I linked to

mattly21:09:05

basically I turned those into first-class subscriptions, even though they're single-purpose

mattly21:09:34

is there any way to turn off the console warnings for overriding event and sub handlers?

danielcompton21:09:38

@mattly you can swap out the loggers for your own ones

danielcompton21:09:47

but that’s a brute force solution

mattly21:09:47

hm, I still want to get the deprecation warnings for the old register-sub and such though

samueldev23:09:38

Is there any known issues w/ using update-in in my event handlers?