Fork me on GitHub
#re-frame
<
2016-05-26
>
gregg00:05:46

@pbaille: that will be a bug. Could I please get you to submit an issue here: https://github.com/Day8/re-com/issues. Thanks.

kauko11:05:04

How would re-frame handle a situation where I have 3 buttons that all do the same thing (thing A), and later I'll want one of the buttons to do things A and B? Should I have separate events for each of them from the start (`:button1-pressed`, :button2-pressed), or can I compose events somehow?

kauko11:05:27

btw, couldn't re-frames README benefit from having a full example in the bottom? I've read the README a while back but I've never used re-frame, but sometimes when I come back it'd be nice to get the "whole picture" quickly. Just to remind myself.

kauko11:05:48

the readme itself is superb, as has been said many times.

mikethompson11:05:17

@kauko At the bottom of the readme it has a "Where To Go" next section which points to: https://github.com/Day8/re-frame/tree/master/examples

kauko11:05:29

Yeah, I saw them 🙂 But wouldn't it be nice if there was one final code block that showed all the "keywords" (dispatch, subscribe), and how they're connected together?

kauko11:05:39

I don't know if this makes sense. It does to me! 😄

mikethompson11:05:26

@kauko: regarding your other queston, hard to say exactly, but I think I'd make the two buttons dispatch differently

snoe19:05:10

It's possible to have the A-B handler do B and dispatch to A