Fork me on GitHub
#re-frame
<
2018-02-10
>
mikethompson00:02:08

This is good writing and interesting observations: https://cambium.consulting/articles/2018/2/8/the-power-of-clojure-debugging I'm happy to say they appear to have been partially influenced by the philosophy in the re-frame-trace README (they reference it). Maybe. I might be over reading it.

Vincent Cantin05:02:16

Do you know where to find re-frame project examples featuring multiples 'components' in a may that keep large codebase organized? I am looking for an example of https://github.com/Day8/re-frame/blob/master/docs/Basic-App-Structure.md#larger-apps

mikethompson05:02:53

/docs/ExternalResources.md

Vincent Cantin14:02:53

I am wondering how exactly the query functions get 'automatically called' when the state of the app-db is changed. Are they all called and their result diff-ed with their previous result? (I mean the ones which are extracting values from the db)

Vincent Cantin15:02:19

Does re-frame have some ways of calling only the query functions it knows will be affected by a db-state change?

mikerod15:02:24

@vincent.cantin they are all tracked via the reagent reaction mechanism.

mikerod15:02:35

If they are called, the first check is if their arguments are =

itruslove22:02:28

@mikethompson thanks, we put a lot of effort into that article so I'm happy to hear that. I think re-frame-trace is an indispensable tool but I can't honestly say it influenced my debugging philosophy. I can say that re-frame has very much influenced me. Thanks for all your amazing contributions!

hoppy23:02:41

anybody have suggestions with how to deal with a canvas element that needs some of itself redrawn when a subscription fires? I'm going a little crazy with this.....

hoppy23:02:09

ok, that IS interesting. Thank you @p-himik