This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-26
Channels
- # announcements (10)
- # asami (15)
- # babashka (200)
- # beginners (48)
- # calva (56)
- # cider (6)
- # clara (2)
- # cljs-dev (18)
- # cljsrn (6)
- # clojars (3)
- # clojure (23)
- # clojure-czech (2)
- # clojure-europe (41)
- # clojure-germany (5)
- # clojure-italy (19)
- # clojure-nl (5)
- # clojure-uk (8)
- # clojurescript (60)
- # clojureverse-ops (5)
- # cursive (14)
- # datomic (6)
- # events (1)
- # figwheel-main (5)
- # graalvm (17)
- # honeysql (2)
- # instaparse (1)
- # integrant (9)
- # jobs (5)
- # music (2)
- # off-topic (37)
- # other-languages (1)
- # pathom (10)
- # proletarian (5)
- # quil (3)
- # reagent (39)
- # reitit (4)
- # remote-jobs (3)
- # reveal (6)
- # rum (9)
- # shadow-cljs (27)
- # vrac (3)
- # xtdb (5)
Yeah, I’ve noticed the same thing when working on making the job-handler a function. It really is a logical consequence. I’m trying a version where the job-handler is a function in production at work this week, and I’m going to try your suggestions for making retry-strategy a function and removing the job-type, too. It’s not a lot work - rewriting the documentation is what takes time! 🙂
I have this commit running in production at work now: https://github.com/msolli/proletarian/commit/ee4155a1063710c09f412a0ebf2ac76bdfffdddf I’ll look into making retry-strategy a function too. I’ll cut a new release after that change (if it sticks).
> I suggest that there’s naming updates to move that into some kind of flavour. I’m not sure I get what you mean here? :face_with_raised_eyebrow: