Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor conda info to better accomodate different display backends (e.g. "stand library", "JSON", or "rich") #13692

Open
2 tasks done
Tracked by #13707
travishathaway opened this issue Mar 14, 2024 · 0 comments · May be fixed by #13755
Open
2 tasks done
Tracked by #13707
Assignees
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

Comments

@travishathaway
Copy link
Contributor

travishathaway commented Mar 14, 2024

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

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?

  • Experiment around with different design patterns such as Abstract Factory to see what would work best for displaying stdout.
  • The design pattern chosen should easily be able to accommodate a new display library such as rich, but do not implement rich right now.
  • The refactored code should function identically to the previous code (use tests to verify this)
  • Submit a draft pull request so we can discuss proposes solution(s)

Additional Context

No response

@travishathaway travishathaway added type::feature request for a new feature or capability source::anaconda created by members of Anaconda, Inc. in-progress issue is actively being worked on spike issue is for doing research work or prototyping; outcome is optional and not required labels Mar 14, 2024
@ForgottenProgramme ForgottenProgramme linked a pull request Apr 2, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: 🏗️ In Progress
Development

Successfully merging a pull request may close this issue.

2 participants