polylith

2024-12-17T21:48:15.971629Z

polylith uses the following component directory structure in its docs…

components/
├── foo-component
│   ├── deps.edn
│   ├── resources
│   ├── src
is something like this possible instead?
components/
├── dir-a ;; organizing components under a new directory
│   └── foo-component
│       ├── deps.edn
│       ├── resources
│       ├── src
poly check returns 0 components when i do this, which implies it’s not supported, but it seems valuable to be able to group components this way.

👍 1
tengstrand 2024-12-17T22:14:54.544149Z

No, nested directory structures are not supported.

Joe R. Smith 2024-12-17T23:41:07.719999Z

What's the idiomatic way to "group" components (e.g., by type)?

seancorfield 2024-12-17T23:52:31.492179Z

Use a naming convention so that alphabetic sorting does what you want/need.

👍 1
seancorfield 2024-12-17T23:54:59.035939Z

At work, we've tended to name components mostly by <subsystem>-<component> or <domain>-<component, so we have a bunch of billing-* components, profile-*, photo-*, but we also have google-*, etc.

seancorfield 2024-12-17T23:56:20.808619Z

Polylith:
   24 bases 294 files 76178 total loc,
   169 components 499 files 70880 total loc,
   24 projects 7 files 630 total loc,
  total 800 files 147688 total loc.
Current size of our codebase.