Dependency graph that shows how constraints (module boundaries) are configured #22626
Replies: 13 comments
-
|
This could be done using something like Mermaid or maybe @ngneat/dag. Of course, it could make sense to use the same packages as used to generate the project dependency graph. |
Beta Was this translation helpful? Give feedback.
-
|
We should consider more advanced scenarios such as both |
Beta Was this translation helpful? Give feedback.
-
|
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Beta Was this translation helpful? Give feedback.
-
|
Still looking for feedback. |
Beta Was this translation helpful? Give feedback.
-
|
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Beta Was this translation helpful? Give feedback.
-
|
Please keep it active. |
Beta Was this translation helpful? Give feedback.
-
|
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Beta Was this translation helpful? Give feedback.
-
|
No, no. no. Please keep it active. |
Beta Was this translation helpful? Give feedback.
-
|
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Beta Was this translation helpful? Give feedback.
-
|
Still of big interest. |
Beta Was this translation helpful? Give feedback.
-
|
I dig this idea: once I start adding tags and constraints, it gets difficult surprisingly fast to keep the rest of the team up to date with what is a perfectly clear picture in my mind. I'd like to have it as a "view" in the current |
Beta Was this translation helpful? Give feedback.
-
|
We need this also. Am going to work on a local implementation for now, if it goes well I'll try to port it to an MR here. As monorepos become big this will be a much more useful and easier to reason about graph than the standard nx one |
Beta Was this translation helpful? Give feedback.
-
|
+1 Would be super helpful to increase visibility of large monorepos. |
Beta Was this translation helpful? Give feedback.
-
Description
A "dependency graph" like visualization that reads the main
.eslintrc.jsonortslint.jsonfiles in a workspace and shows how the constraints (module boundaries) are configured.Motivation
When working with multiple tag values, it can become quite hard to keep track of which tag can import from which. A visual representation will make it easier to see the connection between tags. This will also make it possible to identify unused tags and/or unintentional links between libraries (i.e. libraries that can unintentionally import from or be imported in other libraries).
Suggested Implementation
Basic sketch based on the screenshot above (Paint for the win).
(The refresh icon signifies that the tag can import other libraries with the same tag)
Alternate Implementations
Beta Was this translation helpful? Give feedback.
All reactions