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.No, nested directory structures are not supported.
What's the idiomatic way to "group" components (e.g., by type)?
Use a naming convention so that alphabetic sorting does what you want/need.
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.
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.