Provide way to structure projects by components
HBehrens opened this issue · comments
While many projects choose to map their logical components to their source folder hierarchy there are exceptions and cases where you want to provide an independent, hierarchical perspective. You also might want to look at cross-cutting aspects.
By describing a hierarchy of named nodes with a set of include/exclude file patterns and include/exclude symbol patterns per node you should be able to resolve this. There is the need of multiple of such hierarchies.
Similar to today's ability to browser the folder hierarchy you will be able to look at all the children of a node + an implicit "other" for all the unmatched symbols captured by the node itself.