Fork me on GitHub
#re-frame
<
2017-08-25
>
lumpy02:08:10

@stvnmllr2 have you checked out re-frisk? It gives you an interactive view of app-db along with all the events that have fired

stvnmllr202:08:15

I have. it's great. But not in prod 🙂

deg07:08:13

@danielcompton Thanks, will do. I'm away for the weekend but will tackle this in a few days.

kah0ona07:08:56

Hi people, I just wanted to say thanks for this project. I now have 5 web apps in production (of which two are pretty sizeable) for various clients, and couldn’t ‘ve been happier how the code base turned out. Especially since the later versions of re-frame, things are really really nice. Thanks to everyone who contributed.

kah0ona07:08:10

It’s such a joy to work with, in combination with figwheel

kah0ona07:08:58

Glad to say it’s now pretty much full-time for me as well, got enough going on to not have to do other stuff 🙂

sandbags11:08:10

@danielcompton trace looks very useful, thanks for shouting about it

samueldev12:08:37

just wanting to make people (& @mikethompson ) aware of this comment thread:

samueldev13:08:23

where I feel re-frame (+cljs) is the closest thing to a silver bullet that I've come across in my 7 years of UI development, I'd love to see options added to re-frame to support (in this case) other DOM libraries, rather than fragmenting the userbase

reefersleep15:08:01

@deg the interaction with figwheel and the many unknowns to me in your code (all the functions and returned values) makes it impossible for me to say anything specific on the topic. But my 2 cents are; 1. When something in my applications have re-rendered endlessly, it’s usually because my component somehow updates the data that is passed into it. This may be through many layers of indirection, but it’s usually the same story: component is called with data x, fires off data-store change y, which causes the component to be called with data x’, which fires off data-store change y’, which causes the component to be called with data-store change y’‘'… you get the picture. In your case, you are not talking about re-rendering, rather the subscription being called, but I would still look for the same thing in this way in order to ensure that it isn’t the case; identify the components where you deref this particular subscription and verify that the component is or is not caught in a loop of this sort. 2. Reduce the code (and functionality) of your subscription function until the error subsides, then reintroduce functionality until it reappears in order to identify the elements causing the behavior. Maybe this is newbie advice, but it’s worth being reminded of 🙂 And it comes to my mind exactly because there are unknown functions and values (to me) in your code - sometimes I can succesfully debug other people’s code this way without having to understand all of it, just by pinpointing some silly mistake in a call chain. Usually wrongly shaped data or a desired side effect with undesired side effects 😄 Sorry if this is obvious stuff.

theeternalpulse16:08:19

With inject-coefx, how do I pass a coeffect handler an argument passed into the event handler function. Say I have an event that needs the result from an ajax call, I want to make a call in ajax but need to pass in the argument from the original event handler. The documentation doesn't seem to cover that case

theeternalpulse22:08:29

also is there a good guide on managing syncing from the re-frame db store and an actual external source, best practices and such?