Clojurians Log v2
re-frame
What’s the advantage of using:
(reg-sub
:root-comp-initial-tab
:<- [:_id]
(fn [id _]
(if id "Tabs" "Sign In")
))(reg-sub
:root-comp-initial-tab
(fn [db _]
(if (:_id db) "Tabs" "Sign In")
))
@ps There's also https://day8.github.io/re-frame/subscriptions/#why-layer-2-extractors
It helps a lot if [:_id] is not just a path in the db, but a rather complicated subscription which is not easy to replicate as a function from db
@p-himik "In this particular case - none." Is that strictly correct? I thought RF, given the explicit :id subscription, would avoid propagating to :root-comp-initial-tab if sth other than :id changed in db.
That's true. But in this particular case, the :root-comp-initial-tab subscription is as simple as it can get - it won't matter at all.
In fact, if :_id is only used by :root-comp-initial-tab, then that might be a disadvantage even. At the very least, just because of the extra code involved.
I was thinking it important for a noob to RF to grok the short-circuiting of state propagation by RF, regardless of the de facto insignificance in the given use case. No? Still not sure if @ps picked that up, though the doc is indeed extensive.
In this particular case - none.
can you describe a case where the former pattern would be better than the latter?
As is almost always the case, it's described rather well in the excellent re-frame documentation, which IMO everybody working with re-frame should read in full at least once. https://day8.github.io/re-frame/subscriptions/#the-four-layers
Yes I’ve read this. But it doesn’t tell why pass in signals instead of accessing the dB directly even in layer 3
Is it more efficient?
I have an issue with my react component not correctly subscribing to a value. This is my view:
(let [Stack (createStackNavigator)]
[:> (.-Navigator Stack) {:initialRouteName @(subscribe [:root-comp-initial-tab])}
[:> (.-Screen Stack) {:name "Sign In" :options {:headerShown false}
:component (reactify-component google-signin-comp)}]
[:> (.-Screen Stack) {:name "Tabs" :options {:headerShown false}
:component (reactify-component tabs)}]])@(subscribe [:root-comp-initial-tab]. This is the registration:
(reg-sub
:root-comp-initial-tab
:<- [:signed-in-status]
(fn [signed-in? _]
(let [returning (if signed-in? "Tabs" "Sign In")]
(prn "returning " returning)
returning)
))It looks like you’re using some js components and it’s hard to tell how exactly they treat the values you pass inside them.
From what you saying, it looks like the subscriptions are working fine.