fpm icon indicating copy to clipboard operation
fpm copied to clipboard

Option to output module dependency tree

Open rouson opened this issue 3 years ago • 4 comments

Description

I assume that fpm constructs some form of module dependency tree. It would be nice to have an option that prints the dependency tree for a project. This is especially useful for a developer who encounters a new project that doesn't have such information in the documentation. Specifically, if one is going to contribute to a project, dependency information can be really useful in determining the number of places that could be impacted by changes in one given place.

Possible Solution

Add a --dependency-tree flag that prompts the printing of whatever data structure fpm uses to store this information.

Additional Information

No response

rouson avatar Apr 06 '22 22:04 rouson

Similar question in #682.

milancurcic avatar Apr 07 '22 01:04 milancurcic

@milancurcic I just realized that #682 addresses a different topic but related topic. I'm referring to module dependencies, which might be mostly internal and could exist even in a project with no dependencies on external projects. I've added the word "module" in this issue's title and initial comment to make my request more clear. I'm seeking information that's useful for refactoring. Seeing a module dependency tree could be very helpful in determining which modules could be impacted by changes in any given module.

rouson avatar May 01 '22 20:05 rouson