polylith
polylith copied to clipboard
Introduce a tree structure into the `components` and `bases` subdirectories
Is your feature request related to a problem? Please describe. Having the workspace components (and maybe bases) semantically grouped in some way, e.g. by purpose, by layer, etc.
Describe the solution you'd like
Introduce a tree structure into the components and bases subdirectories, so that the dir structure like this is possible:
...
- components
- domain
- domain-component-a
- domain-component-b
- services
- service-component-a
- service-component-b
...
Describe alternatives you've considered
- Support for multiple workspaces (see #431 and #470). Now reverted.
- The only workaround atm is prefixing the component names, e.g. "domain-component-a". This sucks a bit, since the separator options are limited to
-and_, since a component name have to be a valid file name.
Additional context Already discussed this feature in Slack channel and here as a partial alternative to multiple workspaces support.