Skip to content

Option to output module dependency tree #687

Open
@rouson

Description

@rouson

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions