Fork me on GitHub
#re-frame
<
2019-02-01
>
pyr14:02:32

Hey! I just open-sourced a tiny re-frame utility we've been using a lot at Exoscale: a pull-request queue visualizer to ensure we don't have too many in-flight PRs: https://github.com/exoscale/pullq

victorb14:02:55

Does it have backoff for the GitHub API? I'm part of a group of organizations under the same company, five github organizations and in total ~500 github repos. Would it handle that out of the box?

pyr23:02:02

I'm interested in knowing if it works out for you. We have fewer members and repos and haven't hit any limits

WhoNeedszZz14:02:05

Late to seeing this, but I'd be interested if it had Gitlab support.

pyr14:02:48

re-frame made this a successful weekend endeavor

victorb14:02:09

That's really cool @pyr! You should share it in #announcements, looks like a generally useful tool, re-frame or not 🙂

Jacob Haag21:02:10

Is there a way to pass a parameter to a subscription that does a computation? The subscription that is used for the computation takes a parameter. See example below

(register-sub
 :cart-items            
 (fn [db [_ category]]
   (get-in db [:cart category :item])))

(rf/reg-sub
 :cart-count
 (fn [_] ; <--- this is where the param would theoretically go
   (rf/subscribe [:cart-items]))
 (fn [items]
   (count items)))

Charles21:02:26

Is there any good way to make the app-db be thread local? I'm using re-frame concurrently on the clj side of things and want each request to have a clean / separate app-db

hoopes23:02:51

has anyone used a good declarative notification lib? all the react ones i’ve seen so far seem to want you to call addNotification or somesuch on a manager of some kind. Would be cool to throw some map in the app db, and there’s a for loop somewhere to render them. (Or am i way off base with my thinking?)