clj-commons

hlship 2023-03-21T19:31:40.811429Z

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

👍 1
👍🏻 2
hlship 2023-03-21T21:53:48.634639Z

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

🎉 3
hlship 2023-03-21T21:56:58.423819Z

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.

borkdude 2023-03-21T22:40:53.972249Z

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

seancorfield 2023-03-21T22:46:49.489879Z

Different coordinates so that's OK?

👍 2
seancorfield 2023-03-21T22:47:09.313469Z

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

borkdude 2023-03-21T22:47:20.447689Z

yep, makes sense

dpsutton 2023-03-21T22:49:30.115089Z

means the namespaces need to be completely disjoint then right?

hlship 2023-03-21T23:10:40.783719Z

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

borkdude 2023-03-21T23:33:59.052629Z

@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

hlship 2023-03-21T23:35:21.816499Z

So not ; works for me.