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

RichConsole: Prettify m1 CLI console using rich #4806 #5123

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

gziz
Copy link
Contributor

@gziz gziz commented Jan 21, 2025

Why are these changes needed?

As requested in #4806

  • Use the rich library to prettify the console.
    • Using Panel to wrap the messages
    • Different colors for each agent in M1.
  • As suggested by @gagb, placing user to the left, Orchestrator in the middle and any other agent to the left.

Some screenshots:
image
image

Checks

Copy link

codecov bot commented Jan 21, 2025

Codecov Report

Attention: Patch coverage is 0% with 88 lines in your changes missing coverage. Please review.

Project coverage is 69.84%. Comparing base (44b9bff) to head (d03c8e9).

Files with missing lines Patch % Lines
...es/autogen-ext/src/autogen_ext/ui/_rich_console.py 0.00% 86 Missing ⚠️
...ackages/autogen-ext/src/autogen_ext/ui/__init__.py 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5123      +/-   ##
==========================================
- Coverage   70.39%   69.84%   -0.56%     
==========================================
  Files         174      176       +2     
  Lines       11083    11171      +88     
==========================================
  Hits         7802     7802              
- Misses       3281     3369      +88     
Flag Coverage Δ
unittests 69.84% <0.00%> (-0.56%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@gagb
Copy link
Collaborator

gagb commented Jan 24, 2025

@gziz and @ekzhu the only remaining issue is lack of code coverage. Should we do that now or later?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants