-
Notifications
You must be signed in to change notification settings - Fork 881
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+128
−167
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
5734f98
refactor: update app buttons to use the new button component
BrunoQuaresma 8140292
Add AgentButton back
BrunoQuaresma 2a39826
FMT
BrunoQuaresma 5853a55
Fix styles
BrunoQuaresma 662cc94
Fix vscode button styles
BrunoQuaresma 7a0e645
Merge branch 'main' into bq/refactor-agent-button
BrunoQuaresma 591da07
Improve selector
BrunoQuaresma 9d2e4e2
Merge branch 'bq/refactor-agent-button' of https://github.com/coder/c…
BrunoQuaresma df9a7ed
Fix selector
BrunoQuaresma File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,31 +1,8 @@ | ||
import Button, { type ButtonProps } from "@mui/material/Button"; | ||
import { Button, type ButtonProps } from "components/Button/Button"; | ||
import { forwardRef } from "react"; | ||
|
||
export const AgentButton = forwardRef<HTMLButtonElement, ButtonProps>( | ||
(props, ref) => { | ||
const { children, ...buttonProps } = props; | ||
|
||
return ( | ||
<Button | ||
{...buttonProps} | ||
color="neutral" | ||
size="xlarge" | ||
variant="contained" | ||
ref={ref} | ||
css={(theme) => ({ | ||
padding: "12px 20px", | ||
color: theme.palette.text.primary, | ||
// Making them smaller since those icons don't have a padding around them | ||
"& .MuiButton-startIcon, & .MuiButton-endIcon": { | ||
width: 16, | ||
height: 16, | ||
|
||
"& svg, & img": { width: "100%", height: "100%" }, | ||
}, | ||
})} | ||
> | ||
{children} | ||
</Button> | ||
); | ||
return <Button variant="outline" ref={ref} {...props} />; | ||
}, | ||
); |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.