Skip to content

refactor: refactor activity in workspace page #17980

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

Merged
merged 4 commits into from
May 22, 2025

Conversation

BrunoQuaresma
Copy link
Collaborator

Changing the activity in the workspace page. It is more boring, but more reliable and extensible. By moving it to the bottom of the agent card, we have more space to display longer messages and more items. It also give us some space for interactivity controls in case we want them in the future.

Before:
Screenshot 2025-05-21 at 19 09 41

After:

Screen.Recording.2025-05-21.at.19.10.32.mov

@BrunoQuaresma BrunoQuaresma requested review from a team and jaaydenh and removed request for a team May 21, 2025 22:16
case "failure":
return theme.palette.error.main;
return "text-content-warning";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be text-content-destructive?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure. I use warning for "alerts" and destructive for "actions". Eg. A failure is just warning the user about an error, but delete, is an action that destroy things. Makes sense?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it depends on the context and the feature, I have been using destructive for error alerts and warning for warning alerts because sometimes there are both.

Copy link
Contributor

@jaaydenh jaaydenh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall this is an improvement for the UI and nice to see updates to use Tailwind.

I am guessing that this was originally placed closer to the top of the page originally for demo purposes but the current location feels more useful if you wanted to review many logs at once.

@BrunoQuaresma
Copy link
Collaborator Author

@jaaydenh I updated the design to include the app statuses in the agent row after @bpmct feedback and requests to make it higher priority in the page.

@BrunoQuaresma BrunoQuaresma requested a review from jaaydenh May 22, 2025 12:56
@BrunoQuaresma BrunoQuaresma merged commit 6f0defb into main May 22, 2025
33 checks passed
@BrunoQuaresma BrunoQuaresma deleted the bq/refactor-activity-on-workspace-page branch May 22, 2025 16:05
@github-actions github-actions bot locked and limited conversation to collaborators May 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants