This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-22
Channels
- # ai (1)
- # announcements (1)
- # babashka (9)
- # beginners (18)
- # calva (19)
- # clerk (136)
- # clj-http (3)
- # clj-kondo (13)
- # cljs-dev (166)
- # clojure (39)
- # clojure-europe (133)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-uk (12)
- # clr (1)
- # community-development (6)
- # conjure (8)
- # cursive (13)
- # data-science (1)
- # datomic (26)
- # events (5)
- # fulcro (12)
- # gratitude (3)
- # honeysql (9)
- # hyperfiddle (33)
- # introduce-yourself (6)
- # kaocha (1)
- # lambdaisland (5)
- # malli (4)
- # off-topic (3)
- # rdf (4)
- # re-frame (3)
- # releases (3)
- # scittle (11)
- # specter (2)
- # sql (4)
- # tools-deps (4)
- # vim (10)
Could get-owner
fn be added to babashka.fs to simulate java.nio.file.Files/getOwner
?
Moreover, having ->link-opts
public would be handy - any thoughts on that?
@U06BE1L6T Hey, seems reasonable. Can you post one (or two?) issues at babashka.fs?
If I understand it correctly, you can specify dependencies in either bb.edn
or deps.edn
. Which one is preferred, and why?
bb.edn
is for the local project only (tasks, scripts). the deps in here are never shared with other projects.
deps.edn
is for when you're creating libraries
you can use the dependencies from deps.edn
in bb.edn
by writing:
{:deps {my.awesome/project {:local/root "."}}}
always use a unique symbol for your project, similar to when you would use the library in other projectsNice, concise explanation! (Maybe might be a place for this in a babashka FAQ or similar)
it is described here already but maybe not sufficiently: https://book.babashka.org/#project-setup