/ alire Public
Automatically narrow down dependencies given as "any" #675
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.
npmalso works like this. When a user adds a dependency without giving a version range, after this PR we use the solved version to narrow down the dependency to be added to what the user probably intends. E.g.:
alr with foopreviously resulted in
foo*being added; now it will result in either
foo^x.y, etc being presented as the requested dependency.
*dependency can still be added by requesting it explicitly with
alr with 'foo>=0'(or manually editing, of course).
This may merit a config option to disable this behavior.