fix: Pretty print short result for mamba search by default#4066
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4066 +/- ##
=======================================
Coverage 51.21% 51.21%
=======================================
Files 239 239
Lines 28666 28666
Branches 3009 3009
=======================================
Hits 14681 14681
Misses 13982 13982
Partials 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Is there any chance of this being merged? Or is there anything that prevents it from being merged? It is a 1-character change only. |
|
@jjerphan Any chance you could have a look at this? Just getting any sort of feedback would be really appreciated. |
jjerphan
left a comment
There was a problem hiding this comment.
Thank you for the heads-up; could you add at least a non-regression test?
|
I will see what I can do ... It looks like there are at least some tests for pretty-printed output in |
|
I added a test to the
|
b74c9a7 to
f04be1e
Compare
mamba search by default
f04be1e to
6a3678d
Compare
jjerphan
left a comment
There was a problem hiding this comment.
Thank you, @kuepe-sl!
I just have rebased your branch onto main.
I think that there are many other UX elements of mamba search which need fixing:
- the version which is being shown is not the latest one
- one should be able to see all the builds of a package without using
*, which show many more things
|
I think there is 1 thing for the UI I'd like to see: a switch Currently, searching for e.g. |
|
Also IMO |
|
Thank you for the fix! Do not hesitate to open issues to track the remaining things you'd like to see in the UI. |
Description
mamba searchwithout wildcards is supposed to auto-enable pretty printing. (with package info)mamba searchwith wildcards should just print everything as a table.Currently, it does the opposite, spamming the terminal with lots of package details when a wildcard is used. (see below for an example with the
opencvpackage)This PR fixes the issue and makes it work the way it should.
Type of Change
Checklist
pre-commit run --alllocally in the source folder and confirmed that there are no linter errors.Other
current output: