This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-20
Channels
- # announcements (16)
- # aws (1)
- # babashka (24)
- # beginners (54)
- # calva (25)
- # cider (4)
- # cljs-dev (2)
- # clojure (16)
- # clojure-dev (39)
- # clojure-europe (18)
- # clojure-nl (1)
- # clojure-uk (4)
- # clojurescript (66)
- # core-async (16)
- # cursive (13)
- # datomic (15)
- # deps-new (1)
- # duct (22)
- # fulcro (20)
- # jobs-discuss (1)
- # kaocha (3)
- # lsp (11)
- # malli (8)
- # off-topic (38)
- # other-languages (18)
- # polylith (18)
- # portal (15)
- # react (2)
- # reagent (9)
- # reitit (7)
- # releases (10)
- # reveal (1)
- # sci (13)
- # shadow-cljs (3)
- # specter (4)
- # sql (4)
- # xtdb (16)
Hi all, is there a recommended tool for checking which projects in a given deps.edn
config are out-of-date?
There’s also https://github.com/Olical/depot
Another big +1 for antq
-- it also checks GitHub Actions workflow files and pom.xml
files and I think a few other things. We run it every day at work to track which dependencies are outdated (we don't update deps every day but it's useful to track "drift").
anyone have a good argument on why to prefer one form over another?
(or (valid-thing? foo)
(throw (ex-info "invalid foo" {})))
(when-not (valid-thing? foo)
(throw (ex-info "invalid foo" {})))
Do you care to return true when the error is not thrown? If so, only the or has that behavior
I think the when-not implies that a side-effect will occur when the predicate is returning false.
In the or
someone is interested in the result (which happens to be either true or an exception).
it's not in a let-bind context so the return value is not needed. its more or less an assertion in an api handler