tools: add output when scanning module in an install query #19934
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.
Since more validation logic is moved out of the final install and update process, it can take longer for a user to get an initial feedback from vpm - it's not an instant
Installing ...
anymore, because the validation is done beforehand. Also, there are cases that don't reach theInstalling <moname>
print already. This PR addsScanning <modname>
print when parsing and validating the install-query to give a user a quicker feedback that the request is being processed and at what state it is.For now, I would continue to keep the outputs simple. After most of the teething problems are fixed, I'm planning to propose color-coded outputs for VPM - probably similar cargo, but we can then discuss on Discord which style is appropriate for V.
馃[deprecated] Generated by Copilot at 1dc786e
Improve
vpm
output by showing scan progress for module identifiers. Add a print statement tocmd/tools/vpm/common.v
.馃[deprecated] Generated by Copilot at 1dc786e
scan_module_identifier
function to parse a module identifier from a string and return a struct with the name, version, and source (link, F0