Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Two first commits are trivial UI improvements.
Third probably needs an explanation. I was almost hit by the situation where I increased the upper bounds of my dependencies, but there aren't valid install-plan which would contain actually newest versions of packages. Therefore I could be given an expression that my package works against new version of some dependency, but actually it doesn't.
For example, if I add
vector: >=0.9 && <0.11
direct dependency toreflex-0.3
:But if I run with
--recursive
flag, I get a lot of output with some interesting information: