Skip to content

Comments

fix: alignment of inputs in settings/general#1725

Merged
MrgSub merged 1 commit intoMail-0:stagingfrom
retrogtx:align-general
Jul 14, 2025
Merged

fix: alignment of inputs in settings/general#1725
MrgSub merged 1 commit intoMail-0:stagingfrom
retrogtx:align-general

Conversation

@retrogtx
Copy link
Contributor

@retrogtx retrogtx commented Jul 14, 2025

bad

image

good

image

Summary by cubic

Fixed alignment and sizing of input fields in the General Settings page for a cleaner, more consistent layout.

Summary by CodeRabbit

  • Style
    • Improved layout and styling of the general settings page for better responsiveness and consistency, especially for language, timezone, and email alias selectors. Labels now use consistent typography, and form controls adapt more fluidly to different screen sizes.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 14, 2025

Walkthrough

This update revises the responsive layout and styling of form controls on the general settings page. Fixed width classes are removed in favor of flexible and container-based width constraints, and label typography is standardized. No changes are made to logic, event handling, or exported entities.

Changes

File(s) Change Summary
apps/mail/app/(routes)/settings/general/page.tsx Removed fixed width classes from form controls, applied flexible widths, and standardized label typography.

Sequence Diagram(s)

Possibly related PRs

Suggested reviewers

  • ahmetskilinc

Poem

The settings page got a gentle touch,
No more widths that squeeze too much!
Labels now look neat and small,
Selects stretch wide, embracing all.
With flexible forms, the UI feels new—
A bunny’s hop toward a sleeker view!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Greptile Summary

This PR addresses alignment issues in the General Settings page form inputs. The changes primarily focus on standardizing input widths and improving responsive behavior:

  • Mobile views now use full-width inputs (w-full)
  • Desktop views have fixed widths (200px-280px) for better visual consistency
  • Standardized text styling for form labels with consistent font weights and spacing
  • Improved hover states and layout structures

The changes make the form more visually consistent and improve usability, especially on mobile devices. The improvements are clearly demonstrated in the before/after screenshots provided.

Confidence score: 5/5

  1. This PR is very safe to merge as it only contains styling changes to form elements
  2. The changes are well-contained within the general settings page and don't affect any functional logic
  3. No files need special attention as the changes are straightforward CSS modifications

1 file reviewed, no comments
Edit PR Review Bot Settings | Greptile

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🔭 Outside diff range comments (1)
apps/mail/app/(routes)/settings/general/page.tsx (1)

60-66: Add type="button" to prevent accidental form submission

The Button acting as the pop-up trigger sits inside the <form id="general-form">.
Without an explicit type, HTML buttons default to submit, so clicking the timezone selector would POST the whole settings form unintentionally.

-<Button
-  variant="outline"
-  role="combobox"
-  aria-expanded={open}
-  className="flex !h-9 w-full items-center justify-start rounded-md hover:bg-transparent"
+<Button
+  type="button"               // avoid implicit submit
+  variant="outline"
+  role="combobox"
+  aria-expanded={open}
+  className="flex !h-9 w-full items-center justify-start rounded-md hover:bg-transparent"
🧹 Nitpick comments (1)
apps/mail/app/(routes)/settings/general/page.tsx (1)

199-206: Consider DRYing up repeated arbitrary-width utilities

md:w-[200px] and md:w-[280px] appear in several places.
If more inputs adopt the same sizes, maintaining scattered magic numbers becomes brittle. A small extracted CSS utility (e.g. .form-col-sm, .form-col-lg) or a Tailwind theme extension would centralize the constraint and simplify future tweaks.

Also applies to: 223-226, 234-249

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ec8ce2 and f8d794c.

📒 Files selected for processing (1)
  • apps/mail/app/(routes)/settings/general/page.tsx (5 hunks)
🧰 Additional context used
🧠 Learnings (1)
apps/mail/app/(routes)/settings/general/page.tsx (2)
Learnt from: retrogtx
PR: Mail-0/Zero#1468
File: apps/server/src/trpc/routes/mail.ts:331-331
Timestamp: 2025-06-28T03:56:09.376Z
Learning: In apps/server/src/trpc/routes/mail.ts, the user indicated they are not using ISO format for the scheduleAt parameter, despite the frontend code showing toISOString() usage in the ScheduleSendPicker component.
Learnt from: retrogtx
PR: Mail-0/Zero#1328
File: apps/mail/lib/hotkeys/mail-list-hotkeys.tsx:202-209
Timestamp: 2025-06-18T17:26:50.918Z
Learning: In apps/mail/lib/hotkeys/mail-list-hotkeys.tsx, the switchCategoryByIndex function using hardcoded indices for category hotkeys does not break when users reorder categories, contrary to the theoretical index-shifting issue. The actual implementation has constraints or mechanisms that prevent hotkey targeting issues.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: cubic · AI code reviewer
🔇 Additional comments (1)
apps/mail/app/(routes)/settings/general/page.tsx (1)

199-206: Visual width tweaks look good & consistent

Moving the fixed widths from the inner SelectTrigger/Button to the surrounding FormItem keeps controls full-width on small screens while preserving predictable alignment for md and up. Nice, tidy change.

Also applies to: 223-226, 234-249

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

cubic reviewed 1 file and found no issues. Review PR in cubic.dev.

@MrgSub MrgSub merged commit 6b2c04a into Mail-0:staging Jul 14, 2025
6 checks passed
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.

2 participants