You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find it annoying that ] test always dumps the whole manifest before running tests. I'm almost never interested in that info and it's just noise to me most of the time. If I was designing the feature in the first place I would have made this an optional switch ([--verbose] or maybe [-m|--manifest]) and not include it by default. But probably now people rely on having that output captured. So a switch like [--quiet] that suppresses that output would seem like the way to go.
I'll probably contribute the PR for this myself, it's probably a quick one, but I'm opening the issue in case it's already been discussed or is already out there in some existing PR.
The text was updated successfully, but these errors were encountered:
The reason it is shown is that package versions during tests are not always the same as what you are running with in normal cases and you also have the extra test-specific dependencies and knowing the version of those is probably also useful. I agree that it is a bit verbose.
Could the two newer methods for specifying test-specific dependencies listed in #3953 not fix this, by not relying on ] test specific magic to handle the additional dependencies?
I find it annoying that
] test
always dumps the whole manifest before running tests. I'm almost never interested in that info and it's just noise to me most of the time. If I was designing the feature in the first place I would have made this an optional switch ([--verbose]
or maybe[-m|--manifest]
) and not include it by default. But probably now people rely on having that output captured. So a switch like[--quiet]
that suppresses that output would seem like the way to go.I'll probably contribute the PR for this myself, it's probably a quick one, but I'm opening the issue in case it's already been discussed or is already out there in some existing PR.
The text was updated successfully, but these errors were encountered: