Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detective cannot map linkage between containing module and inner modules #35

Open
tomwhite007 opened this issue Nov 7, 2024 · 0 comments

Comments

@tomwhite007
Copy link

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

image

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.

image

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.

image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant