This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-21
Channels
- # announcements (26)
- # babashka (115)
- # babashka-sci-dev (5)
- # beginners (48)
- # calva (69)
- # cider (4)
- # clj-commons (11)
- # clj-kondo (1)
- # cljfx (29)
- # clojure (109)
- # clojure-art (1)
- # clojure-czech (1)
- # clojure-europe (33)
- # clojure-nl (1)
- # clojure-nlp (3)
- # clojure-norway (7)
- # clojure-uk (1)
- # clojurescript (63)
- # clr (1)
- # data-science (41)
- # datalevin (1)
- # datomic (11)
- # emacs (58)
- # etaoin (11)
- # figwheel-main (1)
- # fulcro (5)
- # google-cloud (12)
- # helix (2)
- # honeysql (21)
- # hyperfiddle (22)
- # joyride (53)
- # malli (52)
- # off-topic (27)
- # portal (4)
- # re-frame (19)
- # releases (3)
- # ring-swagger (5)
- # xtdb (30)
Before I hit the transfer button, this is a good moment to consider the repo name, which is currently "clojure-humanize"; would just "humanize" be better ("clojure-" feels redundant)?
Transfered. https://github.com/clj-commons/humanize. It's public. I'll work on renaming namespaces and such soon.
I guess it's good to go through this process with something relatively trivial. That being said, I really like this library, because I'm all about good feedback.
wouldn't renaming namespaces be a breaking change? or it this an intentionally clean start?
(as I did with HoneySQL -- so you can have code depending on both transitively without conflict)
@hlship This is what I've settled on for digest: https://github.com/clj-commons/digest/blob/master/src/clj_commons/digest.clj
which had a single-segment namespace, but this caused issues with graalvm. I left the single segment namespace + added clj-commons.digest