This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-07
Channels
- # announcements (20)
- # babashka (25)
- # beginners (48)
- # biff (26)
- # calva (5)
- # cider (3)
- # clara (7)
- # clerk (7)
- # clj-kondo (61)
- # cljdoc (3)
- # clojure (6)
- # clojure-austin (1)
- # clojure-conj (8)
- # clojure-europe (58)
- # clojure-nl (1)
- # clojure-norway (4)
- # clojure-poland (1)
- # clojure-uk (9)
- # cursive (2)
- # emacs (11)
- # fulcro (8)
- # graphql (14)
- # gratitude (6)
- # humbleui (10)
- # hyperfiddle (17)
- # integrant (15)
- # introduce-yourself (1)
- # leiningen (5)
- # malli (13)
- # meander (21)
- # nbb (11)
- # off-topic (15)
- # pedestal (15)
- # polylith (15)
- # quil (28)
- # rdf (2)
- # reitit (3)
- # releases (6)
- # sci (21)
- # shadow-cljs (38)
- # spacemacs (3)
- # xtdb (6)
As my personal code garden is growing, I have started to use sub namespaces in my development directory. They basically record different approaches and mini tutorials (quasi) as repl sessions. They are a nice stepping stone before writing components and I can jump back into a topic more quickly!
I’m just getting started with Polylith, so I’m wondering if there’s such a thing as a multilingual (e.g. mixed CLJ and Python) Polylith repo.
Probably not. The poly
tool only supports .clj
but Polylith as a concept applies to all languages -- but you won't get checking and incremental testing support etc in other languages.
And .cljc
.
kind of what I figured. but as I said, still getting my feet wet and learning the tooling.
No, .cljs
is not supported by the poly
tool.
A workspace can also be created https://polylith.gitbook.io/poly/architecture/workspace#existing-git-repository another monorepo, which can be useful sometimes.
If your not aware there is also https://github.com/DavidVujic/python-polylith no idea if you would be able to use one monorepo and both tools in the same repo.
Do you suppor having the workspace not living at the root of the repository, but instead as a sub directory @U018VMC8T0W?
The Python tooling is only aware of one workspace currently, so you would have to navigate into that workspace to use the tool, though.