This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-04
Channels
- # announcements (3)
- # babashka (14)
- # beginners (151)
- # calva (14)
- # cider (9)
- # clj-kondo (24)
- # cljdoc (12)
- # cljs-dev (195)
- # cljsjs (3)
- # cljsrn (13)
- # clojars (12)
- # clojure (234)
- # clojure-dev (3)
- # clojure-europe (9)
- # clojure-greece (1)
- # clojure-italy (2)
- # clojure-japan (4)
- # clojure-nl (4)
- # clojure-spec (89)
- # clojure-taiwan (1)
- # clojure-uk (16)
- # clojuredesign-podcast (2)
- # clojurescript (17)
- # conjure (11)
- # core-async (4)
- # core-typed (31)
- # cursive (9)
- # datomic (8)
- # emacs (17)
- # figwheel (1)
- # fulcro (5)
- # ghostwheel (42)
- # graphql (3)
- # hugsql (5)
- # jackdaw (3)
- # jobs-discuss (93)
- # joker (4)
- # meander (6)
- # mount (1)
- # off-topic (23)
- # pathom (10)
- # re-frame (23)
- # reitit (7)
- # remote-jobs (18)
- # shadow-cljs (153)
- # spacemacs (24)
- # sql (30)
- # tools-deps (14)
- # vim (12)
- # xtdb (1)
@jake142 There are a couple of options: 1) add rewrite-clj to babashka. 2) implement as a pod. 3) implement as a bb-like spin-off, say a rewrite-clj-cli
.
About 1: these criteria should be considered: https://github.com/borkdude/babashka#including-new-libraries-or-classes
About 2: the pod approach works well with pure data back and forth or managing some stateful references on the pod side. But rewrite-clj is quite record and protocol-centric which makes it harder to work with as a pod. Maybe something like https://github.com/carocad/parcera could work better in a pod since it returns pure EDN.
About 3: This will definitely work.
Note that there are already a few bb-like CLIs based on sci: bootleg, dad, spire. There could be another one (as described in option 3).
@jake142 Did an experiment with wrapping parcera here. Seems to work well! https://github.com/babashka/pod-babashka-parcera
I wonder if there’s a world where the config for specific kondo rules could point to some kind of fix
script? Perhaps kondo itself could even communicate with parcera using the pod protocol
I think it's better to keep clj-kondo separate from these scripts. It can output the data that these tools need to build upon. One example of such a tool is https://github.com/borkdude/carve. Carve could now be re-implemented using babashka + pod-babashka-parcera.
hello everyone, Im running a shell command with (sh my-nice-command)
but the results are a bit weird
{:exit 0, :out "", :err "\rUpload complete.\n\r .." }