Closed weavejester closed 10 years ago
:+1: this bit us when trying to use friend, because we were using camel-snake-kebab in a middleware.
@trptcolin: Thanks for reporting. Can you explain how this bit you?
I'll fix this within a few days now that I know it actually affects normal usage. I was previously under the impression that this only matters when trying to access the library straight from Java code (without using the Clojure API).
Oh, I mis-pattern-matched, sorry. Will open a separate issue for my thing.
For what it's worth, I tend to avoid libraries with single-package namespaces, as I don't know all the circumstances under which they break. I don't want to find myself with a weird error when I enable AOT compilation, or something requires me to interoperate with Java.
It might be that I never run into issues, but why take the risk?
For the record: I will change the namespace if I do another backwards-incompatible change or if somebody gets hit by this issue.
Single-part Clojure namespaces have some issues when integrating with Java, because they're compiled into classes that lack a containing package. Consider a two-part namespace instead (e.g.
camel-snake-kebab.core
orcamel-snake-kebab.conversions
).