tree 29769b2b67ffa75505dd6b8adb96f63567652c38
parent eaf365138c6f46b3ae04b1d7ac0f340c3840bcc0
author Jonas Finnemann Jensen <jonasfj@google.com> 1636638663 +0100
committer GitHub <noreply@github.com> 1636638663 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhjR/HCRBK7hj4Ov3rIwAArEgIALFQOkQ6idjKOw4vDzfrL8qX
 IHrCo0itZc91BhLHUpu2GthLRBBEBVF/57HwlZRFPZatpY2xJQmHSv8Bzc7+fu9p
 oSyARQxknL5ReQxiTfgCCWoes0lHr+lOUW3BiH81GF5BQCpAbTQsSFm8MCLFQDns
 8qFWyBxmtIwoHQHTfh0SBhF6j56Ug0b531h7qMlZDP0jHmU0IRKv9QoU3dWbKp0V
 GPccfr2Q3xYLhmMDsWim4u1nakHDShm2rCwtud2bi3zubHg99hJHdAdJcg4U/rDG
 P4SGIlLA5RpSKMhhllOfvxbFkWrFnw2bzz8FR7rZjOJEZ/+kEwdBQKyRN6LmCkc=
 =jTFS
 -----END PGP SIGNATURE-----
 

Better error messages round 2 (#3223)

* Refactor notices/hints for solver conflicts.

Untangled a lot of type assertions and digging into details of the
incompatibility when printing the incompatibility. Notably, we introduce
a concept of notices and hints.

Notices are messages that an `IncompatibilityCause` can have, they are
human readable messages printed before the incompatibility explanation.
This allows `SdkCause` to point out the current version of an SDK that
is causing a conflict (if the SDK is available).

Hints are messages that an `IncompatibilityCause` can have, they are
human readable message with actionable hints to be printed after the
incompatibility explanation. This allows `PackageNotFoundCause` to hint
that trying without `--offline` might work.

Hints are printed after the incompatibility explanation because they
actionable, they don't serve to explain what went wrong. They are
intended to be actionable, hence, it's preferable the user sees these as
one of the first things.