Skip to content

Conversation

@jaaydenh
Copy link
Contributor

@jaaydenh jaaydenh commented Oct 7, 2025

No description provided.

@jaaydenh jaaydenh self-assigned this Oct 7, 2025
@jaaydenh jaaydenh changed the title chore: migrate appearanceform to Tailwind, shadcn chore: migrate appearanceform to Tailwind and shadcn Oct 7, 2025
@jaaydenh jaaydenh requested review from a team and BrunoQuaresma and removed request for a team October 7, 2025 22:04
@jaaydenh jaaydenh marked this pull request as ready for review October 7, 2025 22:06
Copy link
Member

@aslilac aslilac left a comment

Choose a reason for hiding this comment

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

I was kinda dreading this one. but it looks great! thanks!

Comment on lines -1 to -7
import type { Interpolation } from "@emotion/react";
import CircularProgress from "@mui/material/CircularProgress";
import FormControl from "@mui/material/FormControl";
import FormControlLabel from "@mui/material/FormControlLabel";
import Radio from "@mui/material/Radio";
import RadioGroup from "@mui/material/RadioGroup";
import { visuallyHidden } from "@mui/utils";
Copy link
Member

Choose a reason for hiding this comment

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

that's a satisfying chunk of imports to watch vanish

Copy link
Contributor

@buenos-nachos buenos-nachos left a comment

Choose a reason for hiding this comment

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

Your changes look good to me. Just wanted to flag a couple of spots in the code that I think could be cleaned up while we're touching the file

</div>
</Section>
<div css={{ marginBottom: 48 }}></div>
<div className="mb-12" />
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we still need this empty div? Does the Section component not support className?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nice catch, moved the mb-12 to Section as a className

</RadioGroup>
</FormControl>
<RadioGroup
aria-labelledby="fonts-radio-buttons-group-label"
Copy link
Contributor

@buenos-nachos buenos-nachos Oct 8, 2025

Choose a reason for hiding this comment

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

This looks like invalid HTML to me. If we have aria-labelledby, we need another element in the HTML that has (1) an id attribute with a matching value and (2) some kind of labeling text

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added the id to the section title "Terminal Font" span

onChangeTerminalFont(toTerminalFontName(value))
}
>
{TerminalFontNames.filter((name) => name !== "").map((name) => (
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need this filter call, or can we trust the backend-generated types to not include a zero value?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It looks like TerminalFontName in typesGenerated comes from codersdk/users.go with an empty string option. So it seems like we need to filter out the empty string if we don't want to display that.

@jaaydenh jaaydenh merged commit 9935da8 into main Oct 8, 2025
26 checks passed
@jaaydenh jaaydenh deleted the jaaydenh/migrate-appearance-form branch October 8, 2025 20:13
@github-actions github-actions bot locked and limited conversation to collaborators Oct 8, 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.

4 participants