-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: graph showing only the dependent modules #632
Comments
Hi @El-Chiang there's currently no reaches or reachable filter option in the CLI or the API. Besides being a good idea for pull request context I think it'll fulfil a more general need as well - in #469 there was a request for something similar. What CI do you use? related workFor PR's I currently use the --focus option to highlight changed files and all modules they depend on and that depend on them. |
In the CI, it gets all the diff files at every PR and executes the depcruise command to analyze all the modules that depend on these diff files, and finally generates a report. I thought about using the |
Hi @El-Chiang - I've made a stab at a The beta In any case I'm curious whether it helps in your use-case. If you have any feedback it'll be very welcome! |
@El-Chiang FYI - the regular release ( |
Thanks @sverweij! This works great for me 🎉 |
This tool is a great idea! Inspired by it, I added a job to the ci pipeline to analyze the impact (dependants) of each PR. However, our team works on a giant web application, if I show all the dependencies, this graph will be very large and not conducive to checking. So, is there a way only to show the dependants?
Context
Let me give you an example to describe the problem I am facing:
Currently, I configure
reachable
rule and output toerr-report
to solve my need, but I also want to show their dpendency path through the graph, not only html report.Possible Solution
Is it possible to provide a
reaches
CLI option to filter out all dependants (likereachable
rule)The text was updated successfully, but these errors were encountered: