Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

refactor: update app buttons to use the new button component#17684

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
BrunoQuaresma merged 9 commits intomainfrombq/refactor-agent-button
May 6, 2025

Conversation

BrunoQuaresma
Copy link
Collaborator

Related to#17311

  • Replaces the MUI Buttons by the new shadcn/ui buttons. This change allows the reuse of app links, and terminal buttons using theasChild capability from the Radix components
  • Uses the newproposed design
  • Updates the button styles to support image tags as icons
  • Uses the new Tooltip component for the app buttons

Before:
Screenshot 2025-05-05 at 17 55 49

After:
Screenshot 2025-05-05 at 18 05 38

{children}
</Button>
);
return <Button variant="outline" ref={ref} {...props} />;
Copy link
Contributor

Choose a reason for hiding this comment

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

What is purpose of keeping AgentButton around instead of removing it and using Button directly?

Copy link
CollaboratorAuthor

Choose a reason for hiding this comment

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

This is a good question.

Since we want to have the TerminalLink, AppLink, VSCode buttons, etc. visually consistent, and be sure they are always looking the same, I just decided to keep the AgentButton. Of course, we could just set the variant in all these components, but since they are many (around 5 or 6 I guess) it would be easy to forget to update one of them when changing some of the styles (maybe it is not a problem since we have tests).

I'm going to refactor the apps logic very soon, so If I see it is just ok to remove the AgentButton, I will do.

Copy link
Contributor

@jaaydenhjaaydenh left a comment

Choose a reason for hiding this comment

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

Overall, straightforward and looks good. Just had a question about the reason to keep AgentButton.tsx

BrunoQuaresma reacted with heart emoji
@matifali
Copy link
Member

I like the bigger icons. ❤️

BrunoQuaresma reacted with heart emoji

@BrunoQuaresmaBrunoQuaresma merged commit4fa9d30 intomainMay 6, 2025
29 checks passed
@BrunoQuaresmaBrunoQuaresma deleted the bq/refactor-agent-button branchMay 6, 2025 16:26
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsMay 6, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@jaaydenhjaaydenhjaaydenh approved these changes

@ParkreinerParkreinerAwaiting requested review from Parkreiner

@aslilacaslilacAwaiting requested review from aslilac

Assignees

@BrunoQuaresmaBrunoQuaresma

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@BrunoQuaresma@matifali@jaaydenh

[8]ページ先頭

©2009-2025 Movatter.jp