This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-05
Channels
- # announcements (14)
- # aws (7)
- # babashka (28)
- # beginners (16)
- # calva (2)
- # cider (1)
- # clj-commons (8)
- # clj-kondo (29)
- # clojure (213)
- # clojure-europe (39)
- # clojure-losangeles (2)
- # clojure-norway (9)
- # clojure-spec (2)
- # clojurescript (11)
- # community-development (1)
- # conjure (2)
- # cursive (6)
- # datalevin (2)
- # datomic (8)
- # emacs (29)
- # events (1)
- # fulcro (22)
- # graalvm (14)
- # improve-getting-started (1)
- # jobs (1)
- # lambdaisland (5)
- # leiningen (4)
- # lsp (7)
- # malli (13)
- # meander (11)
- # membrane (13)
- # off-topic (23)
- # polylith (9)
- # re-frame (4)
- # reagent (7)
- # reitit (6)
- # releases (2)
- # sql (58)
- # testing (8)
- # tools-deps (18)
- # web-security (2)
Polylith got nice words today at https://news.ycombinator.com/item?id=33081443 "... Polylith ... has given us yet another boost in developer happiness, speed of delivery, and ease of maintenance".
I'm having a hard time finding an explanation for what the :top-namespace
configuration value entails. I am guessing that all of my code must be in namespaces that are prefixed by this value. Is that a correct understanding? Is this documented somewhere that I am not looking?
Yes, the :top-namespace
defines the standard prefix that all namespaces in your repo will have. At work we picked "ws"
because we're World Singles. It just helps ensure that your code won't conflict with third party code (or at least is much less likely to conflict).
As for documentation, "top namespace" is mentioned in several places but I don't think it really explains why it is done.
Awesome, thanks. Our team has been loosely following the Polylith structure for a while now and we are finally getting around to investigating the tool. Seems like we have to conform very closely to what is described in the documentation to start seeing some benefits. We have components scattered throughout a few different directories and it looks like the tool wants us to move them all into a single place. Will be interesting to flesh it all out. Thanks again
We're migrating our legacy monorepo to Polylith. About 2/3rds done at this point. Over 100 components so far. About two dozen projects.
I've blogged about it at https://corfield.org
This looks like a great resource, will check it out!