This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-17
Channels
- # announcements (2)
- # aws (4)
- # babashka (20)
- # beginners (256)
- # calva (15)
- # chlorine-clover (1)
- # cider (12)
- # clj-kondo (25)
- # cljsrn (16)
- # clojure (115)
- # clojure-europe (7)
- # clojure-finland (5)
- # clojure-italy (10)
- # clojure-nl (35)
- # clojure-spec (13)
- # clojure-uk (83)
- # clojurescript (42)
- # code-reviews (81)
- # conjure (8)
- # cursive (6)
- # data-science (1)
- # datomic (3)
- # duct (18)
- # emacs (2)
- # figwheel-main (40)
- # fulcro (21)
- # helix (1)
- # jackdaw (7)
- # java (2)
- # lein-figwheel (5)
- # luminus (1)
- # observability (12)
- # off-topic (32)
- # parinfer (5)
- # pedestal (19)
- # re-frame (5)
- # reagent (8)
- # reitit (17)
- # rewrite-clj (47)
- # rum (19)
- # shadow-cljs (48)
- # spacemacs (4)
- # sql (40)
- # tools-deps (22)
- # vrac (1)
- # xtdb (25)
coolio, clojure-lsp rewrite-cljc upgrade test helped me find one omission in rewrite-clj (and hence rewrite-cljc) otherwise upgrade pretty straightforward https://github.com/lread/clojure-lsp/commits/lread-rewrite-cljc-test
zip/insert-child* fn was missing https://github.com/lread/rewrite-cljc-playground/commit/4eeac8576341cfd0b205e21745b8ca4063b70476
I notice that most users of rewrite-clj don’t use the (ex zip/next ext) fns and use the underlying zipper directly, probably due to the fact that this wasn’t documented very well.
so this is good news for rewrite-cljc, but not terribly exciting for users of rewrite-cljc until I get it up on clojars.
So I’ve tested rewrite-cljc against cljfmt, zprint and clojure-lsp. Happy to try more if anybody has recommendations.
In the short term, I’m gonna head back to cljdoc to finish up a couple of PRs I initiated many moons ago.
I think I want to move to clj-commons before first release. And I am a bit concerned about current namespace handling and potential breaking changes, but if I mark first release at alpha, I guess breaking changes would be ok.
If you're concerned about people having to change their namespaces from rewrite-clj. to rewrite-cljc., I don't think that's breaking. Your lib is a new one
Nah… not worried about that… I think that rewrite-clj -> rewrite-cljc was a good choice.
More worried about offering something up around namespaced maps that isn’t fully considered yet.
Btw, I found a way to have tests run in a GraalVM native-imega. It can be done using a feature branch of babashka, but maybe this can be even a separate project
Cool! I was fiddling around with running rewrite-cljc test suite in GraalVM native-image a while back. Had something working locally but could not get past memory limitations of free CI services. Was thinking of splitting tests into multiple runs to overcome.
so how it works with babashka: you include the library like the other built-in libraries. and then you run the unit tests from source with bb
maybe there can even be a bb spin-off (like bootleg, spire) that includes rewrite-cljc so you can use it for scripting
@lee I've got something similar here: https://github.com/babashka/pod-babashka-parcera
do you keep a list of changes/fixes compared to rewrite-clj(s)? I'd be interested in those for my own fork that's in clj-kondo
Yeah, I think I have been pretty thorough in my migration notes https://github.com/lread/rewrite-cljc-playground/blob/master/doc/design/01-merging-rewrite-clj-and-rewrite-cljs.adoc but probably useful to split out changes/fixes compared to rewrite-clj(s) to separate doc. I’ll make a todo to see if that would work.
So while I’ve been in lurk mode for the last long while, I’ve noticed you remain a whirlwind productivity! But even more whirlwindier and productivitier!
refactor-nrepl upgrade test to rewrite-cljc success https://github.com/lread/refactor-nrepl/commits/lread-rewrite-cljc-test