Improve version solver output #1855
Conversation
We used to produce weird output like "Because no versions of foo match <1.0.0 or >1.0.0 and foo 1.0.0 depends on bar, all versions of foo require bar". Now we're able to just say "all versions of foo depend on bar" without having to derive that.
Previously it was possible for pub not to indicate the source of a hosted dependency even when it was involved in a source conflict.
| 'baz': {'path': '../baz'} | ||
| }).create(); | ||
| await expectResolves(error: equalsIgnoringWhitespace(''' | ||
| Because every version of foo depends on bar any which depends on baz any, |
There was a problem hiding this comment.
The "any" doesn't seem to add much value here and makes it a little harder to read. What do you think of just showing the package name if the constraint includes all versions?
Because every version of foo depends on bar which depends on baz, every version of foo requires baz from hosted.
So, because myapp depends on both baz from path and foo, version solving failed.
?
There was a problem hiding this comment.
I considered that, but I think it makes sense to reproduce the constraints from the packages' pubspecs here even if they're any. Just saying bar depends on baz risks making it unclear that there's no other version of bar that could work.
Also, since we discourage any constraints in real packages, this is unlikely to come up very often in practice.
Partially addresses #1853