Improve dependency graph #166
Description
Summary
Per previous discussions and analysis, Magento core's dependency graph is a mess, such as all modules depending on the admin notifications module.
- What are specific pain points?
- Where and how should those be addressed?
- What specific changes would be needed for us to improve the graph in Mage-OS?
- How can we minimize breaking changes and merge conflicts in the process, if at all?
This is a blocker for creating a minimal Mage-OS distribution metapackage that excludes as much as possible by default. Right now 'as much as possible' is fairly little.
Examples
Reference:
- https://mage-os.org/updates/dependency-graphs-website-and-more/ and @adamzero1's NX graph demo
- MageOS - Dependency Graph Remediation Project (view) plans by @damienwebdev
- https://github.com/damienwebdev/magento2-nx-graph
- https://discord.com/channels/893449664093904936/1371166001885876275 "Mage-OS Minimal Distribution" Discord thread
- https://tree.taiga.io/project/mage-os-mage-os-technical-initiatives/us/73?kanban-status=9349604 Taiga task
Proposed solution
Use NX graph to determine
- Modules with hidden/missing dependencies that should be evaluated or fixed
- Leaf nodes that can be easily removed
- Cyclical dependencies
- Modules with inappropriate dependencies that should be corrected if at all possible
Release note
No response
Triage and priority
- Severity: S0 - Affects critical data or functionality and leaves users without workaround.
- Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
- Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
- Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
- Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.