Join GitHub today
cmd/go: separate direct and indirect dependencies in go.mod #27887
To summarize, the ordering of the
A proposed fix would be...
What version of Go are you using (
changed the title from
cmd/go: separate direct and indirect dependencies in go.mod
Sep 27, 2018
Note, the list of indirect dependencies in your
That said, a more useful way to look at your dependencies is
@jamesgoodhouse I understand this is not exactly what you asked for, but note that
Here is the
In contrast, for that same example above, a
Again, I understand it might be more convenient to be able to more easily see direct vs. indirect in
The build definition file in any system should be easily readable and understandable. I understand that typically
Simply adding a blank line and separating the direct and indirect dependencies would go a long way in cleaning up the presentation of the
Adding some notes per a discussion with @DemonWav on Slack.
In my experience with modules thus far, a) I never made changes to a
I agree that it's easier to glance at your
To answer the question “what are the modules that provide the direct imports of my non-test packages?”, you could do something like:
See also #27900.
It's valuable to can read
However about the annoying