This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-05
Channels
- # babashka (1)
- # beginners (75)
- # clojure (8)
- # clojure-uk (7)
- # clojurescript (14)
- # code-reviews (6)
- # conjure (5)
- # cursive (13)
- # data-science (1)
- # datomic (46)
- # fulcro (10)
- # helix (15)
- # jackdaw (1)
- # jobs-discuss (10)
- # jobs-rus (1)
- # off-topic (17)
- # pathom (1)
- # re-frame (19)
- # releases (1)
- # spacemacs (9)
- # sql (29)
- # test-check (18)
- # tools-deps (6)
- # xtdb (3)
@p-himik I've been considering writing a tool which ensures your top level dependencies are at least newer than those required by your dependencies
That may be useful. 👍 Although not for my problem in particular because I ended up just dropping the explicit dependency. :)
We've discussed that at length with Sean just a bit above. :) It's not that wrong in my particular context, I think.
tl;dr: I depend on the library, but I don't depend on the version of the library. And if something breaks, the app just won't start. So by not using an explicit dependency, I cannot really run time runtime errors. But with an explicit dependency, I definitely can if I forget to update it along with other libraries that depend on it as well.
it would probably be pretty easy to read a trace file (or use the api and the trace data returned) to see that