Refactor conda info
to better accomodate different display backends (e.g. "stand library", "JSON", or "rich")
#13692
Labels
in-progress
issue is actively being worked on
source::anaconda
created by members of Anaconda, Inc.
spike
issue is for doing research work or prototyping; outcome is optional and not required
type::feature
request for a new feature or capability
Checklist
What is the idea?
To prepare for implementing a different display backends in conda (e.g. rich) and to refactor current code, we want to first perform a small scale refactor on
conda info
to what lessons can be learned.Why is this needed?
To prepare for a larger refactor of the conda code.
What should happen?
Additional Context
No response
The text was updated successfully, but these errors were encountered: