Add feature to show actual dependencies between packages

[doodzik]

This is a really great gem, and it helps see the dependencies laid out like that. 🙂

I was playing around with Graphwerk, and I noticed that it generates a graph on the dependencies' ideal state rather than the actual dependencies. It seems like it doesn't consider deprecations or packages that don't enforce privacy/dependencies. Having that information could help to notice problems and make it easier to create an overview of what is happening in the code. Is there a way to create a graph with the actual dependencies between packages?

[samuelgiles]

@doodzik glad to hear you find it useful 😃

Yes so right now it's using the data Packwerk::PackageSet makes available which comes straight out of the package yml files so as you say its displaying that "ideal" state presuming dependencies are being enforced.

I reckon it'd be pretty easy to use Packwerk::DeprecatedReferences to show deprecated references in the diagram too 👍

As for producing a graph based on actual dependencies, I mean I guess all the information is present via the constant discovery & reference lister logic so it would be possible to map the actual dependencies rather than trust the yml files. Perhaps even a mode where it could even go as far as showing the individual reference points though the graph would be pretty crazy! If I get some time I might dig into this as I'm interested in taking a better look at how the reference checking stuff all works.