You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: Detective cannot map linkage between containing module and inner modules
I have created a demo Nrwl Nx repo to try out Barrel-less module boundary enforcement with Sheriff using a composite of the examples in the Nrwl Enterprise Angular Monorepo Patterns book. I've used Sheriff to make the features as container libs so that the sub-modules (e.g. feature, data, ui, util) are child folders within the Nx libs.
The problem
I want to use Detective to map out the entire repo, including the apps, Nx libs, and the child Sheriff modules, all as one tree. However, Detective UI checkbox options only allow me to see the outer container modules or the linkages between inner folder modules, not both together.
Example 1:
Detective with all the Nx apps and Nx lib root folders ticked
Example 2:
Detective with all Nx apps and Shared lib folders ticked but with the child internal modules ticked to show the leaf modules. Note how the lazy-loaded features in bookings have no links at all and overlap each other.
Example 3: How I want it to be...
Nx Graph with my own sketched lines showing how the container modules are arranged. This one shows all the modules I want to see, but only because it's taken from an old demo of Enterprise Angular Monorepo Patterns using only @nx/enforce-module-boundaries.
Summary
Sheriff and Detective are clearly the way forward for mid-tier enterprise modularised Angular mono repos. I'm grateful for what you guys have done so far. But without a pretty diagram of the full structure of the repo, I can't sell the pattern to my stakeholders.
The text was updated successfully, but these errors were encountered:
Issue: Detective cannot map linkage between containing module and inner modules
I have created a demo Nrwl Nx repo to try out Barrel-less module boundary enforcement with Sheriff using a composite of the examples in the Nrwl Enterprise Angular Monorepo Patterns book. I've used Sheriff to make the features as container libs so that the sub-modules (e.g. feature, data, ui, util) are child folders within the Nx libs.
The problem
I want to use Detective to map out the entire repo, including the apps, Nx libs, and the child Sheriff modules, all as one tree. However, Detective UI checkbox options only allow me to see the outer container modules or the linkages between inner folder modules, not both together.
Example 1:
Detective with all the Nx apps and Nx lib root folders ticked
Example 2:
Detective with all Nx apps and Shared lib folders ticked but with the child internal modules ticked to show the leaf modules. Note how the lazy-loaded features in bookings have no links at all and overlap each other.
Example 3: How I want it to be...
Nx Graph with my own sketched lines showing how the container modules are arranged. This one shows all the modules I want to see, but only because it's taken from an old demo of Enterprise Angular Monorepo Patterns using only
@nx/enforce-module-boundaries
.Summary
Sheriff and Detective are clearly the way forward for mid-tier enterprise modularised Angular mono repos. I'm grateful for what you guys have done so far. But without a pretty diagram of the full structure of the repo, I can't sell the pattern to my stakeholders.
The text was updated successfully, but these errors were encountered: