Fork me on GitHub
#clj-commons
<
2023-03-21
>
hlship19:03:40

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)?

4
👍 2
hlship21:03:48

Transfered. https://github.com/clj-commons/humanize. It's public. I'll work on renaming namespaces and such soon.

🎉 6
hlship21:03:58

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.

borkdude22:03:53

wouldn't renaming namespaces be a breaking change? or it this an intentionally clean start?

seancorfield22:03:49

Different coordinates so that's OK?

👍 4
seancorfield22:03:09

(as I did with HoneySQL -- so you can have code depending on both transitively without conflict)

borkdude22:03:20

yep, makes sense

dpsutton22:03:30

means the namespaces need to be completely disjoint then right?

hlship23:03:40

org.clj-commons.humanize is what I'm planning on

borkdude23:03:59

@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

hlship23:03:21

So not ; works for me.