[WIP] Give reasons for resolving group (#3008)

[TeaDrivenDev]

This is a work in progress to discuss whether this is detailed enough, and a few questions I have about the code.

[TeaDrivenDev]

This is only to bring in the type to avoid having to fully qualify

The alternatives I currently see are

• opening the DependencyChangeDetection module; not sure if we'd want to do that here
• specifying the type and module every time in the pattern match, which seems ugly
• moving the original type somewhere else, like to Paket.Domain; not sure if that would be correct

[TeaDrivenDev]

This addresses #3008 opened by @mavnn.

I have "surfaced" the information about specific changes that cause the resolver to be run for a group, and when that decision is made, every single individual reason for resolving is listed.

One question is what the desired amount of detail for the different cases is. Currently

• all the different NuGet changes are listed individually; if there are multiple changes for a single package, all of them will be listed
• if the framework restriction for a group changes, every single package will also be listed as having a framework restriction change; that probably doesn't make much sense
• remote file changes will say "Remote file x changed in project y"
• settings changes will only say "Group has settings changes"

Is there anything that should have more or less detail?

Ignore the individual commits and changes to files other than DependencyChangeDetection.fs and UpdateProcess.fs; I will rebase and clean those up later.

[forki]

?

[TeaDrivenDev]

@forki That's one of the things to.... ignore. ;-) I used that to set a final breakpoint for debugging and didn't want to sort out what to commit while this is still unfinished. As I said, I'll clean everything up when I finish the PR.

[mavnn]

My personal feeling (@forki may have better ideas) is that if the resolver is triggered because of a change to paket.dependencies that's probably expected behaviour and shouldn't produce any output (except maybe with a verbose flag set?).

Apart from that, listing every package and why it's triggering the resolver sounds useful to me?