@aaelony did you include [day8.re-frame/tracing-stubs "0.5.1"]in your production devs?

They’re in the template to be added, but mustn’t be being added

Or maybe the uberjar isn’t using that profile

@aaelony Sorry, I meant dependencies and not devs.

If different components require one (re-rfame/subscribe ...) what should to do pass it to components arguments or register it within each component separately?

I explore the todomvc example and notice that the components have not props. Does Re-frame suggest to avoid props in components?

@al.vyguzov: Not sure if I understand the question - are you trying to call the same component in different places so that they rely on different subscriptions to get the data they need?

No, the different components use the same subscription. This components put in each other hierarchically

And I try to realize what way is more right. Put this subscription to props or register it in different components separately

@al.vyguzov just subscribe at each place where you need it... no need to pass around the sub reactions

Hi, does anyone have any idea why I might be getting a “no subscription handler registered for..” message for a subscription that, I’m 99% sure it’s reg-sub has been read in? I’ve required the namespace that contains the reg-sub in the namespace where the subscribe is. I’ve also played around with requiring it in the initial/core namespace just to be sure and still seeing the issue. i was also looking to see if there was any logging or something I could turn on that might help but i didn’t see any in the source

probably a typo, hard to tell without the source

yeah I’ve verified that it’s not that 😞 it was working fine, It’s not even somethign I’ve changed. But I

I’ve been working on a macro that would dynamically create subs based on a DSL (basically to setup calculated fields on a form).. This was one of the basic ones that was inline in the code, so that makes it even weirder

I know it's not related to your current problem, but creating a macro to dynamically register subs is probably wrong in 2 ways 1) nothing prevents you from registering subs from a defn (i.e. no macro needed) 2) subs take arbitrary arguments so you could use an argument instead of dynamically generated sub identifiers

hmm, ok i thought about that too. But then there was the thing of avoiding overly generic subs lol

I’m just thinking, I thought I needed to

have the functions, etc setup

these are level 3 subs

So basically in my DSL this:

[:sf425/cash-on-hand
                   [:calc/subtract [:sf425/cash-received :sf425/cash-disbursed]]]

(re-frame.core/reg-sub
  :sf425/cash-on-hand
  (clojure.core/fn
    [___51800__auto__ ___51800__auto__]
    [(re-frame.core/subscribe [:form/cur-field :sf425/cash-received])
     (re-frame.core/subscribe [:form/cur-field :sf425/cash-disbursed])])
  (clojure.core/fn
    [args__51801__auto__]
    (fema-gmm.components.forms.calculations/run-calc
      :calc/subtract
      args__51801__auto__)))

I read about that problem at re-frame doc, but I forget where exactly :((

ill poke around in there

Ok, it’s fixed but I have no idea why lol. There was something weird going on, in another component that caused an error unrelated to subscriptions, etc after the one I described. Yet fixing that fixed my issue

oh well lol

Hi @sveri, I can confirm that adding [day8.re-frame/tracing-stubs "0.5.1"] to :dependencies does fix the issue of the lein uberjar failing to build. That should likely be added to the lein re-frame template as well. Many thanks

https://github.com/Day8/re-frame-template/issues/69

what should you use for an initial db state for an item that is an api response? i’m not sure how to do this since cljs-ajax and cljs-http both use async calls.

or should i just be setting the initial db to a map of what i expect to be returned?

@chadhs: I usually leave that part of my app-db either empty or with some default empty structure/value - as long as you populate it later with assoc-in it doesn't seem to cause any issues

@chadhs this project has an appraoch for more complex initial state setup https://github.com/Day8/re-frame-async-flow-fx

Hey @joelsanchez you were right, got it all working and no macro hell

#_(defn gen-calc-sub
  "Create the level 3 subscription.  If the field is in calcs, it's a calculated field
  and we should directly subscribe to it, otherwise subscribe to the actual field value"
  [calcs [field [calc args]]]
  (print "creating sub for: " field)
  `(rf/reg-sub
     ~field
     (fn [_# _#]
       ~(mapv (fn [arg] (if (calcs arg)
                          `(rf/subscribe [~arg])
                          `(rf/subscribe [:form/cur-field ~arg]))) args))
     (fn [args#]
       (calc/run-calc ~calc args#))))
(defn gen-calc-sub
  [calc-fields [field [calc args]]]
  (let [level-2-func-vec (mapv
                           (fn [arg] (if (calc-fields arg)
                                       (rf/subscribe [arg])
                                       (rf/subscribe [:form/cur-field arg]))) args)
        level-2-func (fn [_ _] level-2-func-vec)
        level-3-func (fn [args] (calc/run-calc calc args))]
    (rf/reg-sub field level-2-func level-3-func)))

#_(defmacro gen-calc-subs
  [calcs]
  (print "creating subs for: " calcs)
  (let [calc-fields (set (map first calcs))                 ;for quick membership test
        ]
    `(do ~@(map #(gen-calc-sub calc-fields %) calcs))))

(defn gen-calc-subs
  [calcs]
  (let [calc-fields (set (map first calcs))]
     (doseq  [calc calcs] (gen-calc-sub calc-fields calc))))

hi @eoliphant glad you got it working! 🙂