This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-08
Channels
- # announcements (14)
- # babashka (12)
- # beginners (140)
- # calva (2)
- # cider (22)
- # clj-commons (14)
- # clj-kondo (49)
- # cljdoc (34)
- # clojure (92)
- # clojure-europe (41)
- # clojure-france (2)
- # clojure-new-zealand (2)
- # clojure-nl (2)
- # clojure-norway (60)
- # clojure-uk (17)
- # clojured (2)
- # clojurescript (7)
- # community-development (3)
- # conjure (2)
- # cryogen (13)
- # cursive (4)
- # data-oriented-programming (2)
- # datahike (5)
- # datomic (12)
- # defnpodcast (10)
- # events (2)
- # fulcro (20)
- # gratitude (3)
- # honeysql (4)
- # introduce-yourself (3)
- # jobs (10)
- # lsp (58)
- # malli (12)
- # missionary (19)
- # off-topic (8)
- # pathom (18)
- # podcasts (1)
- # polylith (41)
- # releases (1)
- # remote-jobs (3)
- # shadow-cljs (52)
- # spacemacs (1)
- # sql (37)
- # xtdb (19)
Is there a way to decode URI's? e.g., "%20"
becomes " "
Hello again, I think I'd like to use babashka.tasks without bb.edn: I have several "operations" where some are dependent on another - while others are not. I had this hard-coded and I am now in the process of making this more generic. Playing around with the configuration it occurred to me that it resembles babashka's tasks-structure. I wouldn't like to put this into a bb.edn, though. I would like to be able to define and access the tasks in code and REPL. I think it would be great if :task could be a parameter to the necessary functions in babashka.tasks. Or maybe I could smuggle a facked bb.edn-structure in? If one could change babashka.impl.common.bb-edn...
@steffenglueckselig You can access / run tasks from "code" and in the REPL by using (babashka.tasks/run 'task)
and tasks themselves can just refer to functions in your code without any other logic
if you don't want to use the main bb.edn
for it you can make another one with --config other-file.edn
Maybe that's the way to go - I am new to tasks. Currently I am using clojure.tools.cli to provide additional data to the configuration/task-setup. I'll see what I'll come up with...
I've lost docstrings upon autocomplete in VSCode / Calva. Calva channel can't seem to be able resolve it, perhaps it's a bb-specific change?
Nothing has changed to the bb nrepl implementation regarding docstrings Iately. You could try a couple of older version of bb to make sure it's not on bb's end. /cc @U0ETXRFEW
hey all - just wondering if anyone has mixed a todo.txt parser (or alternative to parser) into their experiments with bb? I’m really keen to use something that is data portable but of course realise that the lack of structure to it makes things difficult 🙂 All pointers very welcome. Thanks!
it’s a plain text ‘todo’ system - http://todotxt.org