Closed fviernau closed 6 months ago
@fviernau, is this still an issue with all the workspace-related improvements that we had for Yarn?
Task: Represent all Yarn worskpace sub-modules by separate
Project
instances in theAnalyzerResult
At least for Yarn2 this already seems to be the case, see this expected result:
Closed as part of backlog grooming. Feel free to comment if you would like to contribute to this.
Task: Represent all Yarn worskpace sub-modules by separate
Project
instances in theAnalyzerResult
which would be more consistent with otherPackageManager
s and maybe overall also better. I'm writing maybe as I'm not sure if the users are interrested in the structure at all assuming it's often times quite fine grained.Until #2146 there was just an incomplete Yarn workspaces support in place following the approach that only the root project definition file is analyzed. #2146 did not change that approach but made some MVP out of it by adding the construction of a dependency tree so that all dependencies appear properly in the generated reports.
For implementing this ticket, one of the below two givens have to be changed as otherwise it's impossible:
...Making that decision would likely be a good starter for working on this ticket.
Note: It seems that dependency trees may become very large. If the size should turn out to be a problem an option to approach this would be to eliminate redundant subtrees. If such elimination would be done it might become questionable whether exposing submodule structure is reasonable as that would allow exclusion on submodule granularity via e.g. path excludes. If one excludes a subproject containing a deduplicated subtree the effect might not be as desired.