Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe pull request applies purely cosmetic changes across a wide range of files. Changes include the addition and removal of blank lines, reordering of import statements and CSS class names, adjustments to indentation and semicolon usage, and standardizing quotation mark usage. These modifications are confined to documentation, UI components, hooks, configurations, and related TypeScript/JSON files. No functional or control-flow logic has been altered. Changes
Possibly related PRs
Poem
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (14)
apps/mail/app/(routes)/settings/layout.tsx (5)
35-35: Updated Class Order for Main Container.
The class names for the outer<div>have been reordered (movingdark:bg-blackto the end). This change is purely cosmetic (Prettier reformat) and should not affect the styling. Please verify that the CSS specificity remains as intended.
47-47: Adjusted JSX Class Order in Resizable Panel.
The reordering of classes in the<div>inside theResizablePanel(placingbg-offsetLightanddark:bg-offsetDarkahead of other classes) is cosmetic. Confirm that this order does not inadvertently change the visual presentation, especially when using utility-first CSS frameworks.
48-48: Minor Reordering in Sticky Header Element.
The class list for the sticky header<div>has been modified by movingp-2afterborder-b. This adjustment is cosmetic; please ensure that the padding and border styles continue to render as expected.
67-67: Skeleton Layout Class Order Updated.
The reordering of classes in the<div>(movingbg-sidebarto the beginning) is a cosmetic update. Verify that this adjustment matches your style guidelines and that there is no impact on CSS specificity.
68-68: CSS Class Reordering in Skeleton Animation.
The class names in the skeleton layout’s inner<div>have been reordered, reflecting Prettier’s formatting. This change is purely stylistic. Confirm that the animation (animate-pulse) and theming (e.g.,bg-muted,md:rounded-2xl) continue to function as expected.README.md (1)
257-259: Add language specifier to code blockThe fenced code block is missing a language specifier, which would improve syntax highlighting.
- ``` + ```bash rm -rf node_modules rm bun.lockb bun install🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
257-257: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
apps/mail/components/ui/sheet.tsx (1)
22-26: Cosmetic ClassName Reordering in SheetOverlay:The reordering of the class names in the
SheetOverlaycomponent (lines 22–26) is purely stylistic. Ensure that the overlay’s visual behavior (animations, positioning, background opacity) remains consistent.apps/mail/i18n/config.ts (1)
14-14: Formatting Consistency: The addition of the trailing comma after the Turkish language entry ensures valid object syntax and facilitates future additions.apps/mail/components/ui/dropdown-menu.tsx (6)
30-30: Consistent Class Ordering: The reordered utility classes inDropdownMenuSubTriggernow follow a standardized sequence, which aids in visual consistency.
48-48: Standardized Class Formatting: Adjusting the order of classes inDropdownMenuSubContentenhances consistency with other styled components in the codebase.
83-83: Utility Class Refactoring: The revised order of classes inDropdownMenuItemcontributes to a more uniform styling approach across components.
99-99: Refined Class Order: Cosmetic reordering of classes withinDropdownMenuCheckboxItemimproves maintainability and visual consistency.
122-122: Optimized Class Name Ordering: The updated class name order inDropdownMenuRadioItemaligns with the project’s style guidelines for utility classes.
157-157: Consistent Separator Styling: Reordering the class names inDropdownMenuSeparatorensures that this component's styling matches the standardized format applied elsewhere.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (142)
.github/CONTRIBUTING.md(4 hunks).github/FUNDING.yml(0 hunks).github/TRANSLATION.md(2 hunks)README.md(9 hunks)apps/mail/actions/brain.ts(1 hunks)apps/mail/actions/connections.ts(1 hunks)apps/mail/actions/extractText.ts(1 hunks)apps/mail/actions/getSummary.ts(1 hunks)apps/mail/actions/mail.ts(6 hunks)apps/mail/actions/utils.ts(1 hunks)apps/mail/app/(auth)/login/login-client.tsx(10 hunks)apps/mail/app/(auth)/login/page.tsx(1 hunks)apps/mail/app/(auth)/zero/login/page.tsx(2 hunks)apps/mail/app/(auth)/zero/signup/page.tsx(4 hunks)apps/mail/app/(full-width)/contributors/page.tsx(10 hunks)apps/mail/app/(routes)/create/layout.tsx(1 hunks)apps/mail/app/(routes)/create/page.tsx(1 hunks)apps/mail/app/(routes)/developer/page.tsx(3 hunks)apps/mail/app/(routes)/layout.tsx(1 hunks)apps/mail/app/(routes)/mail/[folder]/page.tsx(1 hunks)apps/mail/app/(routes)/mail/create/page.tsx(1 hunks)apps/mail/app/(routes)/mail/page.tsx(1 hunks)apps/mail/app/(routes)/mail/under-construction/[path]/back-button.tsx(1 hunks)apps/mail/app/(routes)/mail/under-construction/[path]/page.tsx(1 hunks)apps/mail/app/(routes)/settings/general/page.tsx(2 hunks)apps/mail/app/(routes)/settings/layout.tsx(3 hunks)apps/mail/app/api/auth/early-access/count/route.ts(3 hunks)apps/mail/app/api/auth/early-access/route.ts(2 hunks)apps/mail/app/api/driver/index.ts(1 hunks)apps/mail/app/error.tsx(2 hunks)apps/mail/app/global-error.tsx(1 hunks)apps/mail/app/globals.css(6 hunks)apps/mail/app/page.tsx(1 hunks)apps/mail/components/context/command-palette-context.tsx(1 hunks)apps/mail/components/context/sidebar-context.tsx(1 hunks)apps/mail/components/context/thread-context.tsx(1 hunks)apps/mail/components/create/ai-textarea.tsx(1 hunks)apps/mail/components/create/editor-buttons.tsx(1 hunks)apps/mail/components/create/editor-menu.tsx(1 hunks)apps/mail/components/create/editor.colors.tsx(3 hunks)apps/mail/components/create/editor.link-selector.tsx(2 hunks)apps/mail/components/create/editor.node-selector.tsx(2 hunks)apps/mail/components/create/extensions.ts(2 hunks)apps/mail/components/create/prosemirror.css(7 hunks)apps/mail/components/create/selectors/link-selector.tsx(1 hunks)apps/mail/components/create/selectors/math-selector.tsx(1 hunks)apps/mail/components/create/selectors/node-selector.tsx(1 hunks)apps/mail/components/create/selectors/text-buttons.tsx(1 hunks)apps/mail/components/create/slash-command.tsx(1 hunks)apps/mail/components/create/uploaded-file-icon.tsx(1 hunks)apps/mail/components/home/footer.tsx(1 hunks)apps/mail/components/home/hero-image.tsx(1 hunks)apps/mail/components/home/hero.tsx(4 hunks)apps/mail/components/icons/animated/align-vertical.tsx(1 hunks)apps/mail/components/icons/animated/archive.tsx(1 hunks)apps/mail/components/icons/animated/arrow-left.tsx(1 hunks)apps/mail/components/icons/animated/bell.tsx(1 hunks)apps/mail/components/icons/animated/book-text.tsx(1 hunks)apps/mail/components/icons/animated/cart.tsx(1 hunks)apps/mail/components/icons/animated/check-check.tsx(1 hunks)apps/mail/components/icons/animated/expand.tsx(4 hunks)apps/mail/components/icons/animated/filter.tsx(1 hunks)apps/mail/components/icons/animated/inbox.tsx(1 hunks)apps/mail/components/icons/animated/keyboard.tsx(1 hunks)apps/mail/components/icons/animated/message.tsx(1 hunks)apps/mail/components/icons/animated/moon.tsx(1 hunks)apps/mail/components/icons/animated/more-vertical.tsx(3 hunks)apps/mail/components/icons/animated/reply.tsx(4 hunks)apps/mail/components/icons/animated/search.tsx(1 hunks)apps/mail/components/icons/animated/settings-gear.tsx(1 hunks)apps/mail/components/icons/animated/settings-lines.tsx(1 hunks)apps/mail/components/icons/animated/shield.tsx(1 hunks)apps/mail/components/icons/animated/sparkles.tsx(1 hunks)apps/mail/components/icons/animated/square-pen.tsx(1 hunks)apps/mail/components/icons/animated/sun.tsx(1 hunks)apps/mail/components/icons/animated/trash.tsx(1 hunks)apps/mail/components/icons/animated/users.tsx(1 hunks)apps/mail/components/icons/animated/x.tsx(1 hunks)apps/mail/components/icons/icons.tsx(1 hunks)apps/mail/components/mail/account-switcher.tsx(2 hunks)apps/mail/components/mail/mail-compose.tsx(8 hunks)apps/mail/components/mail/mail-display.tsx(1 hunks)apps/mail/components/mail/mail-skeleton.tsx(1 hunks)apps/mail/components/mail/mail.tsx(1 hunks)apps/mail/components/mail/navbar.tsx(2 hunks)apps/mail/components/mail/reply-composer.tsx(1 hunks)apps/mail/components/mail/search-bar.tsx(20 hunks)apps/mail/components/mail/thread-display.tsx(1 hunks)apps/mail/components/responsive-modal.tsx(2 hunks)apps/mail/components/settings/settings-card.tsx(1 hunks)apps/mail/components/theme/theme-toggle.tsx(2 hunks)apps/mail/components/ui/accordion.tsx(2 hunks)apps/mail/components/ui/account-switcher.tsx(2 hunks)apps/mail/components/ui/animated-number.tsx(2 hunks)apps/mail/components/ui/avatar.tsx(1 hunks)apps/mail/components/ui/button.tsx(1 hunks)apps/mail/components/ui/card.tsx(2 hunks)apps/mail/components/ui/chart.tsx(6 hunks)apps/mail/components/ui/command.tsx(7 hunks)apps/mail/components/ui/context-menu.tsx(8 hunks)apps/mail/components/ui/dialog.tsx(3 hunks)apps/mail/components/ui/drawer.tsx(2 hunks)apps/mail/components/ui/dropdown-menu.tsx(7 hunks)apps/mail/components/ui/input-otp.tsx(3 hunks)apps/mail/components/ui/input.tsx(1 hunks)apps/mail/components/ui/nav-user.tsx(1 hunks)apps/mail/components/ui/popover.tsx(1 hunks)apps/mail/components/ui/radio-group.tsx(1 hunks)apps/mail/components/ui/resizable.tsx(1 hunks)apps/mail/components/ui/scroll-area.tsx(1 hunks)apps/mail/components/ui/select.tsx(4 hunks)apps/mail/components/ui/separator.tsx(1 hunks)apps/mail/components/ui/sheet.tsx(3 hunks)apps/mail/components/ui/sidebar.tsx(1 hunks)apps/mail/components/ui/skeleton.tsx(1 hunks)apps/mail/components/ui/spinner.tsx(1 hunks)apps/mail/components/ui/switch.tsx(1 hunks)apps/mail/components/ui/tabs.tsx(3 hunks)apps/mail/components/ui/text-shimmer.tsx(3 hunks)apps/mail/components/ui/textarea.tsx(1 hunks)apps/mail/hooks/use-copy-to-clipboard.ts(1 hunks)apps/mail/hooks/use-stats.ts(1 hunks)apps/mail/hooks/use-summary.ts(1 hunks)apps/mail/i18n/config.ts(2 hunks)apps/mail/i18n/request.ts(1 hunks)apps/mail/instrumentation.ts(1 hunks)apps/mail/lib/auth-providers.ts(2 hunks)apps/mail/lib/auth.ts(1 hunks)apps/mail/lib/idb.ts(1 hunks)apps/mail/next.config.ts(2 hunks)apps/mail/sentry.client.config.ts(1 hunks)apps/mail/types/speech-recognition.d.ts(1 hunks)apps/mail/types/tailwind.d.ts(1 hunks)crowdin.yml(1 hunks)packages/db/migrations/meta/0016_snapshot.json(8 hunks)packages/db/migrations/meta/_journal.json(1 hunks)packages/db/src/index.ts(1 hunks)packages/db/src/schema.ts(1 hunks)packages/db/tsconfig.json(1 hunks)packages/tsconfig/base.json(2 hunks)packages/tsconfig/nextjs.json(1 hunks)packages/tsconfig/react-library.json(1 hunks)
💤 Files with no reviewable changes (1)
- .github/FUNDING.yml
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md
257-257: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🔇 Additional comments (308)
packages/db/src/index.ts (1)
17-17: Prettier Formatting Update on Export StatementThis change is purely cosmetic, reformatting the export statement with no effect on its functionality. The code remains clear and correct.
apps/mail/sentry.client.config.ts (1)
11-11: Cosmetic Change: Integration Array Formatting UpdatedThe
integrationsproperty is now formatted as a single-line array (integrations: [Sentry.replayIntegration()],), which is consistent with Prettier’s styling. This purely cosmetic change does not affect functionality.apps/mail/types/speech-recognition.d.ts (1)
52-53: Cosmetic Update: Constructor Signature FormattingThe addition of a space between the
newkeyword and the parentheses aligns with the project's formatting standards. This change is purely cosmetic and does not affect functionality.apps/mail/components/ui/avatar.tsx (1)
38-41: Cosmetic Reordering of CSS Classes
The change reorders the Tailwind CSS classes in theAvatarFallbackcomponent from
"flex h-full w-full items-center justify-center rounded-full bg-muted"
to
"bg-muted flex h-full w-full items-center justify-center rounded-full".
Since Tailwind applies these classes independently without a dependency on order, this modification is purely cosmetic and does not affect the component’s functionality or styling.packages/tsconfig/nextjs.json (1)
1-13: Prettier Formatting Applied Consistently.
The JSON structure has been uniformly reformatted for improved readability. There are no functional changes or alterations to the configuration options.packages/db/tsconfig.json (1)
1-6: Cosmetic Reformatting for Consistency.
The file’s structure has been compacted (e.g., single-line arrays for "include" and "exclude") to align with the project’s formatting standards. No functionality has been altered.packages/tsconfig/base.json (1)
1-20: Consistent Formatting Update.
The "lib" property has been condensed to a single line and a newline was added at the end of the file. These cosmetic improvements ensure consistency without impacting the compiler options.apps/mail/next.config.ts (2)
2-2: Import statement uncommented for proper dependency usage.The import for
withSentryConfighas been uncommented, which properly declares the dependency that's being used in the export statement at line 52. This improves code correctness while maintaining the same functionality.
53-87: Improved Sentry configuration readability.The Sentry configuration has been reformatted with:
- Consistent indentation and spacing between sections
- Properly aligned comments
- Clear separation of configuration options with empty lines
These formatting improvements make the configuration more readable and maintainable without changing any functionality.
apps/mail/components/ui/popover.tsx (1)
21-24: Cosmetic Formatting: Tailwind CSS Classname Reordering
The reordering of the Tailwind CSS classes within theclassNameprop improves readability and consistency. Since all utility classes remain present and valid, the functionality is unaffected.apps/mail/components/mail/account-switcher.tsx (2)
29-33: Cosmetic Update: Reordered class names in SelectTrigger
The reordering of class names is purely stylistic (likely from Prettier) and does not affect functionality. Ensure that the desired visual styles (order and specificity) remain as intended.
48-53: Cosmetic Update: Adjusted class names in SelectItem
The changes in the class ordering for the<div>inside theSelectItemare non-functional and enhance consistency with the broader styling guidelines.apps/mail/components/ui/select.tsx (4)
21-24: Cosmetic Update: Reordered class names in SelectTrigger
Prettier has rearranged the class names in theSelectTriggercomponent. This change improves code consistency and readability while maintaining the same styling behavior.
70-74: Cosmetic Update: Reordered class names in SelectContent
The class names in theSelectContentcomponent have been rearranged. These modifications are purely cosmetic, and the conditional application of classes remains intact.
113-116: Cosmetic Update: Refactored class names in SelectItem
The updated order of class names in theSelectItemcomponent enhances readability and follows the new formatting standards without altering functionality.
134-138: Cosmetic Update: Simplified class names in SelectSeparator
Reordering the class names in theSelectSeparatorcomponent is a cosmetic change that aligns with our standardized styling conventions. No functional impact is expected.apps/mail/app/global-error.tsx (1)
23-24: Cosmetic Newline Addition Detected.
The addition of a newline at the end of the file improves readability and adheres to our consistent code formatting guidelines.apps/mail/types/tailwind.d.ts (1)
1-4: Quotation Mark Consistency Achieved.
Changing the module declaration to use double quotes enhances consistency across the codebase without altering functionality.apps/mail/components/ui/spinner.tsx (1)
41-42: Final Newline for Readability.
The addition of a newline at the end of the file helps maintain consistency with our style guide and improves file readability.apps/mail/app/(routes)/layout.tsx (1)
16-17: Trailing Comma Added for Improved Consistency.
The addition of a trailing comma to theshouldRetryOnErrorproperty helps prevent potential syntax issues during future modifications and aligns with our formatting guidelines.packages/db/src/schema.ts (1)
87-89: Trailing Comma Added in Object Literal.
The addition of a trailing comma after thesuggestedReplyfield in thesummarytable definition improves consistency and maintainability, aligning with the project's formatting standards.crowdin.yml (1)
4-4: Standardized String Delimiter forbase_url
The change from single quotes to double quotes in thebase_urlentry is purely cosmetic and improves consistency with the rest of the codebase.apps/mail/i18n/request.ts (1)
9-9: Minor Whitespace Adjustment
The minor modification (adjustment of blank lines) does not affect the logic or functionality of the file and enhances readability.apps/mail/lib/idb.ts (1)
67-68: Consistent File Termination
The addition of a newline at the end of the file is a standard formatting practice that improves file consistency and readability.apps/mail/app/(routes)/mail/under-construction/[path]/back-button.tsx (1)
13-13: Cosmetic ClassName Reordering
Reordering the CSS class names (from"gap-2 text-muted-foreground"to"text-muted-foreground gap-2") is a non-functional, cosmetic change that aligns with the overall formatting consistency of the project.apps/mail/lib/auth.ts (1)
4-5: Improved Import Order
The reordering of the import statements fordrizzleAdapterandgetSocialProvidersis a cosmetic change that enhances readability without impacting functionality.apps/mail/components/ui/skeleton.tsx (1)
3-4: Cosmetic Class Name Reordering.
The change reorders the CSS classes inside thecnfunction (from"animate-pulse rounded-md bg-muted"to"bg-muted animate-pulse rounded-md"). This is purely cosmetic with no impact on functionality and improves consistency with our style guidelines.packages/db/migrations/meta/_journal.json (1)
125-125: Consistent JSON Formatting.
The addition of a newline after the closing brace (line 125) adheres to common JSON formatting practices, ensuring better compatibility with tools that process JSON..github/TRANSLATION.md (1)
44-46: Improved Document Readability.
The introduction of a blank line after the example JSON snippet and the removal of extra whitespace enhance the document’s readability. This adjustment is purely cosmetic and aligns well with Prettier’s output.apps/mail/components/settings/settings-card.tsx (1)
19-24: Enhanced Readability with Reformatting.
Splitting theclassNamestring into a multi-line format in theCardcomponent improves clarity without altering functionality. The reformatted structure aligns with our coding style guidelines.packages/tsconfig/react-library.json (1)
1-8: Uniform JSON Structure.
The revised indentation and removal of a trailing newline result in a more uniform and readable JSON configuration. These changes are cosmetic and do not impact functional behavior.apps/mail/app/(routes)/mail/[folder]/page.tsx (1)
18-18: Cosmetic Simplification of Return Statement
The return statement has been simplified to a single-line JSX return of<MailLayout />, which improves readability without impacting functionality.apps/mail/hooks/use-copy-to-clipboard.ts (2)
1-2: Consistent Formatting in Imports
The imports now use double quotes consistently, which aligns with the prettier configuration and improves overall code style.
4-10: Formatting and Spacing Improvements in Function Body
The formatting adjustments insideuseCopyToClipboard, including proper spacing and indentation (e.g. aroundtoast.successandsetTimeout), enhance readability without modifying logic.apps/mail/components/ui/sidebar.tsx (2)
6-6: Improved Import Order for Clarity
Moving theSidebarProviderimport to an earlier position improves the clarity and organization of the import section. This change is purely cosmetic and aligns with the codebase’s consistency standards.
1-17: Overall Formatting Consistency
The reordering of class names and minor formatting adjustments across the Sidebar component contribute to better readability and maintainability. No functionality or logic was affected by these changes.apps/mail/components/create/uploaded-file-icon.tsx (1)
16-18: Refined Whitespace in Conditional Block
The removal of extra whitespace before theelse if (mimetype.includes("audio"))enhances readability while preserving the original logic.apps/mail/components/mail/reply-composer.tsx (2)
1-11: Reordered Imports for Consistency
TheuseTranslationsimport from "next-intl" has been moved to a higher location within the import block. This change aligns with other files in the codebase and improves consistency without affecting functionality.
15-415: Prettier Formatting Across the Component
All formatting changes—including adjustments in spacing, indentation, and JSX layout—adhere to the Prettier standards and enhance the overall readability of the file. No functional code has been altered.apps/mail/components/ui/radio-group.tsx (1)
24-27: Cosmetic Reordering of Class Names in RadioGroupItem
The reordering of the class names is purely cosmetic and helps maintain consistency across the codebase without affecting functionality.apps/mail/components/ui/textarea.tsx (1)
9-12: Consistent Ordering of Class Names in Textarea Component
The updated className string rearranges the order of classes for improved readability and consistency. This change is cosmetic and does not impact the behavior of the component.apps/mail/components/context/command-palette-context.tsx (1)
15-17: Reordered Import for VisuallyHidden
The adjustment to import the VisuallyHidden component from "@radix-ui/react-visually-hidden" is a cosmetic change that improves the organization of imports. No impact on functionality is expected.apps/mail/components/ui/nav-user.tsx (1)
32-34: Reintroduction of the useTheme Import
Reintroducing theuseThemeimport from "next-themes" ensures proper theme management within the NavUser component. This change increases consistency and restores expected functionality.apps/mail/components/responsive-modal.tsx (1)
45-47: Improved Formatting for DrawerContent
The restructured placement of the{children}prop in the DrawerContent block is a cosmetic change that enhances readability without affecting functionality.apps/mail/components/ui/account-switcher.tsx (2)
52-52: CSS classes reordered for consistencyThe CSS classes have been reordered following Prettier formatting standards. This is a purely cosmetic change with no functional impact.
80-80: CSS classes reordered for consistencyThe CSS classes have been reordered following Prettier formatting standards. This is a purely cosmetic change with no functional impact.
README.md (2)
18-28: Improved markdown formatting with better spacingAdded consistent line breaks before list items for better readability in the markdown source. This improves the visual structure of the document without changing its rendered output.
67-73: Added line breaks for better readabilityAdded line breaks for better readability in the code block sections. This is a purely cosmetic improvement.
apps/mail/components/mail/mail-skeleton.tsx (1)
135-135: CSS classes reordered for consistencyThe CSS classes have been reordered from
"flex items-center p-[7px] border-b"to"flex items-center border-b p-[7px]"following Prettier formatting standards. This is a purely cosmetic change with no functional impact.apps/mail/components/context/sidebar-context.tsx (1)
119-119: CSS classes reordered for consistencyThe CSS classes have been reordered from
"group/sidebar-wrapper flex min-h-svh w-full has-[[data-variant=inset]]:bg-sidebar"to"group/sidebar-wrapper has-[[data-variant=inset]]:bg-sidebar flex min-h-svh w-full"following Prettier formatting standards. This is a purely cosmetic change with no functional impact.apps/mail/components/mail/thread-display.tsx (1)
151-153: Cosmetic CSS Class Reordering:
The<div>wrapping theReplyComposecomponent now uses the class string"relative flex-shrink-0 md:top-2". This is a purely cosmetic change (reordering of CSS classes) that does not affect functionality.apps/mail/components/ui/scroll-area.tsx (1)
37-38: Reordered Class Names for Readability:
The class names for theScrollAreaPrimitive.ScrollAreaThumbhave been reordered to"bg-border relative flex-1 rounded-full". This adjustment is cosmetic and aligns with styling conventions without impacting behavior.apps/mail/hooks/use-stats.ts (3)
1-3: Standardizing Directive and Import Formatting:
The"use client";directive and associated import statements now use double quotes and include semicolons. This aligns the header with the project’s Prettier configuration and improves consistency.
7-12: Enhanced Readability for SWR Hook Declaration:
The useSWR hook declaration has been reformatted with consistent indentation and alignment of generic types. These changes improve readability without affecting functionality.
14-21: Return Object Formatting Improvement:
The return block has been reformatted for better vertical alignment, making the code easier to scan. No functionality has been modified.apps/mail/hooks/use-summary.ts (3)
1-1: Standardized Client Directive:
The"use client";directive now uses double quotes and a semicolon, ensuring consistency with the rest of the codebase.
6-16: Improved SWR Hook Formatting:
The useSWR hook is now formatted with clearer indentation for its parameters and generic type. This change boosts code clarity without impacting behavior.
18-19: Neat Return Statement Formatting:
The return statement is now more streamlined and aligns with the Prettier configuration. This update is strictly cosmetic.apps/mail/components/ui/context-menu.tsx (11)
1-8: Header and Import Standardization:
The"use client";directive and the import statements (lines 1–8) have been updated to use double quotes and include semicolons. These cosmetic changes enhance consistency across the codebase.
21-40: Refactored ContextMenuSubTrigger Component Formatting:
TheContextMenuSubTriggercomponent’s prop types and className composition (including the conditionalinset && "pl-8") are now formatted more cleanly. This improves readability while leaving functionality unchanged.
42-56: Improved ContextMenuSubContent Layout:
The formatting within theContextMenuSubContentcomponent has been tidied—including the className string wrapping—to enhance clarity without altering behavior.
57-73: Enhanced ContextMenuContent Formatting:
TheContextMenuContentcomponent now features restructured indentation and className formatting. This update is purely cosmetic and improves maintainability.
74-91: Consistent Formatting for ContextMenuItem:
TheContextMenuItemcomponent’s formatting—including conditional styling withinset && "pl-8"—has been updated for consistency and clarity. There is no change to its functionality.
92-113: Formatted ContextMenuCheckboxItem:
The formatting adjustments inContextMenuCheckboxItem(such as indentation and className alignment) enhance readability without impacting component behavior.
115-136: Refined ContextMenuRadioItem Layout:
The reformatting withinContextMenuRadioItemimproves clarity and visual structure. These are stylistic changes with no effect on functionality.
137-150: Cleaned Up ContextMenuLabel Component:
TheContextMenuLabelcomponent now uses a more consistent className composition and prop formatting. This cosmetic update aids readability.
151-161: Standardized ContextMenuSeparator Styling:
Minor adjustments to theContextMenuSeparatorclassName formatting have been applied for better consistency. There is no functional impact.
163-172: Consistent Formatting in ContextMenuShortcut:
TheContextMenuShortcutcomponent’s formatting—along with its displayName assignment—has been updated to meet the project’s style guidelines. This is strictly a cosmetic change.
173-190: Streamlined Export Block:
The export statement for all context menu components has been reformatted for alignment and clarity, adhering to the Prettier guidelines. Functional behavior remains unchanged.apps/mail/components/home/hero-image.tsx (1)
6-6: CSS class reordering looks good.The reordering of CSS classes doesn't affect functionality or styling as CSS classes are applied regardless of their order in the className string. These changes are consistent with the prettier formatting applied throughout the codebase.
Also applies to: 12-12
apps/mail/components/create/selectors/math-selector.tsx (1)
1-4: Formatting standardization looks good.The changes standardize quotation marks (single → double) and add semicolons at the end of statements, which are purely cosmetic changes. These modifications improve code consistency across the codebase without affecting functionality.
Also applies to: 7-9, 13-26, 30-30, 34-35
apps/mail/components/ui/switch.tsx (1)
15-15: Focus styles reordering looks good.The reordering of focus-visible styles is a purely cosmetic change that doesn't affect component functionality or appearance. The same styles are still being applied, just in a different order in the className string.
apps/mail/app/(routes)/mail/page.tsx (1)
5-6: CSS class reordering looks good.The reordering of class names in both div elements is purely cosmetic. The new order appears to group related classes together (media queries, dark mode styles), which may improve readability while maintaining the same styling behavior.
apps/mail/app/api/auth/early-access/count/route.ts (2)
2-3: Import uncommented correctly.Uncommenting the imports for
Ratelimitanddbis appropriate as these dependencies are actively used in the code. This change not only improves formatting but also prevents potential runtime errors.Also applies to: 6-6
22-27: Formatting improvements look good.The changes to console.log formatting, blank line additions, and error handling structure are purely cosmetic improvements that enhance code readability without affecting functionality.
Also applies to: 45-46, 49-51, 52-52
apps/mail/components/ui/input.tsx (2)
12-14: Cosmetic Refactor Preserves Functionality
The adjustment to the default value assignment (ensuring that an undefined value defaults to an empty string) and reordering of class names improve readability without affecting behavior.
17-23: Consistent Class Name Ordering
The reordering of the CSS utility classes within theclassNameprop enhances consistency and maintainability. There are no changes to the functionality of the<input>element.apps/mail/components/ui/dialog.tsx (3)
22-25: Improved Overlay Class Formatting
The class names for theDialogOverlaycomponent have been reordered for better readability. These changes are purely cosmetic, and no functional behavior is modified.
39-43: Enhanced Content Styling Readability
The reordering of class names for theDialogContentcomponent makes the styling declarations clearer. The diff preserves functionality while aligning with styling and formatting guidelines.
80-83: Refined Description Class Order
The slight adjustment in the order of class names forDialogDescription(switching from one order to"text-muted-foreground text-sm") is a cosmetic change that does not affect the component's display.apps/mail/components/ui/input-otp.tsx (3)
1-8: Uniform Formatting and Import Reordering
The addition of semicolons, reordering of import statements, and minor punctuation adjustments in this file increase consistency across the codebase. No functional changes are introduced.
13-22: Consistent Component Prop Formatting
Within theInputOTPandInputOTPGroupcomponents, the formatting adjustments (such as trailing commas and spacing) help improve code readability while preserving all existing behavior.
33-59: Contextual Component Adjustments
The changes in theInputOTPSlotandInputOTPSeparatorcomponents, including context extraction and proper assignment of display names, are all stylistic improvements. These modifications follow Prettier’s standard and do not impact functionality.apps/mail/components/ui/animated-number.tsx (2)
1-6: Consistent Quotation and Formatting Updates
Switching to double quotes for the"use client"directive and imports, along with assigning a default value (as = "span"), enhances consistency. These are strictly cosmetic changes aligning with the prettier format.
17-23: Streamlined Return Component
The refactoring of the return statement into a single line simplifies the component's structure and maintains its intended functionality.apps/mail/components/create/selectors/text-buttons.tsx (4)
1-7: Enhanced Import Consistency
The reordering and standardization of import statements (using double quotes and proper semicolon usage) improve consistency in the file without any impact on functionality.
8-23: Clear and Consistent Function Definitions
TheTextButtonscomponent has been reformatted to include semicolons and improved indentation. The refactoredhandleChatWithAIfunction now has clearer structure while preserving its original intent.
24-32: Consistent Array Formatting
The update of theitemsarray (using consistent quotation marks and trailing commas) enhances readability and aligns with the overall prettier formatting applied across the codebase.
34-61: Uniform JSX Formatting
The JSX returned by theTextButtonscomponent has been reformatted for consistency. Button and conditional rendering structures remain functionally identical while becoming easier to read and maintain.apps/mail/app/api/auth/early-access/route.ts (2)
24-26: Email Regex Validation Update:The updated regex pattern (lines 24–26) appears to be a cosmetic reformatting. Please verify that the revised delimiter and any whitespace adjustments still accurately capture all valid email formats without unintended side effects.
38-43: Improved Console Logging Formatting:The multi-line
console.logstatement (lines 38–43) now improves readability without impacting functionality. Confirm that the log output remains as expected in your production environment.apps/mail/components/ui/sheet.tsx (2)
86-89: SheetTitle ClassName Adjustment:The update to the class name for
SheetTitle(lines 86–89) rearranges the order to"text-foreground text-lg font-semibold". This change is cosmetic; please verify that the intended typography and color styling are preserved.
98-101: SheetDescription ClassName Adjustment:The updated class name in
SheetDescription(lines 98–101) now reads"text-muted-foreground text-sm", which is a cosmetic change. Confirm that this alteration does not affect the intended text appearance.apps/mail/components/theme/theme-toggle.tsx (2)
5-6: Import Reordering for Clarity:Moving the
useEffect,useState, anduseThemeimports (lines 5–6) improves consistency and readability. There is no functional impact; please ensure this ordering aligns with your project’s conventions.
38-41: Button ClassName Reordering:The updated CSS class order in the button element (lines 38–41) is a cosmetic change. Verify that hover effects and transition properties (e.g.,
hover:bg-gray-100andhover:text-gray-900) continue to work as expected.apps/mail/components/ui/text-shimmer.tsx (2)
1-6: Consistent String Literal Style:Changing string literals (e.g., the
"use client";directive and import paths) from single to double quotes enhances consistency across the codebase. This is purely a formatting update with no functional changes.
30-35: Motion Component & Animation Props Formatting:The refactoring of the class name strings and animation properties (lines 30–35) is a cosmetic change to improve readability. Please verify that the text shimmer animation renders correctly.
apps/mail/app/(routes)/developer/page.tsx (5)
76-77: Main Container ClassName Reordering:The main container’s class name on line 76 has been reordered (from something like
"flex min-h-screen w-full flex-col bg-background"to"bg-background flex min-h-screen w-full flex-col"). This is a cosmetic change; ensure that the layout and background styling remain unaffected.
79-80: Header Container Styling Update:The header container’s class names (lines 79–80) have been reordered for improved readability. Confirm that the sticky header, blur effect, and backdrop styling are still rendered as intended.
80-85: Back Button Interaction Consistency:The back button’s onClick handler (line 84) and its styling reordering are purely cosmetic changes. No functionality has been affected; however, please double-check that the navigation behavior remains solid.
91-94: Resource Description Styling:The class name reordering in the resource description (lines 91–94) is a cosmetic refinement. Verify that the muted text color and font sizing appear as expected on all devices.
112-118: Card Content & Button Styling Update:The updates to the class names in both the card content (line 113) and the button (line 117) are cosmetic. Confirm that hover states, spacing, and alignment behave correctly during user interaction.
apps/mail/i18n/config.ts (1)
25-28: Enhanced Readability: Reformatting theavailableLocalesexport into a multi-line arrow function improves clarity and adheres to consistent code style.apps/mail/app/api/driver/index.ts (2)
1-2: Cosmetic Import Formatting: The reordering and explicit typing in the import statements enhance clarity. No functional impact noted.
8-20: Clean Code Formatting: Adjustments to the parameter indentation, switch-case structure, and error handling are purely cosmetic and improve readability.packages/db/migrations/meta/0016_snapshot.json (6)
96-97: JSON Formatting Improvement: The foreign key arrays (formail0_account_user_id_mail0_user_id_fk) have been reformatted into a single-line array, which boosts consistency and readability.
191-192: Consistent Array Formatting: The foreign key arrays formail0_connection_user_id_mail0_user_id_fkare now displayed on one line, aligning with the project’s prettified JSON style.
244-246: Streamlined Unique Constraint Formatting: Updating the unique constraint formail0_early_access_email_uniqueto a one-line array format enhances clarity and uniformity.
311-312: Improved Key Array Formatting: The foreign key arrays formail0_session_user_id_mail0_user_id_fkhave been reformatted to improve consistency.
321-322: Uniform Unique Constraint Display: The unique constraint formail0_session_token_uniquenow appears in a concise one-line format, which aids readability.
449-451: Standardized JSON Styling: The unique constraint formail0_user_email_uniqueis now formatted as a single-line array, ensuring style consistency across the schema.apps/mail/app/(routes)/settings/general/page.tsx (3)
20-20: Reordered Import Statements: Moving theuseTranslationsanduseLocaleimports from "next-intl" to an earlier position improves module organization according to the project's style guidelines.
24-24: Consolidated Imports: Grouping the imports forGlobeandClockfrom "lucide-react" clarifies dependency management and aligns with standardized formatting practices.
61-63: Enhanced Readability in Locale Construction: Splitting theIntl.DisplayNamescall across multiple lines increases readability without affecting functionality.apps/mail/components/create/prosemirror.css (8)
4-4: Consistent Font Family Declaration
Changing the font-family to use double quotes (line 4) aligns with our preferred style.
37-40: Standardized Placeholder Content
Updating the&:beforeblock (line 38) to use an empty string with double quotes improves consistency across our CSS rules.
60-63: Consistent Task List Label Styling
The updated rules for the task list labels (line 60) now use double quotes and proper spacing, ensuring uniformity in the stylesheet.
71-79: Refined Checkbox Styling Rules
The reordering and consistent formatting of the checkbox styles (lines 71–79) enhance readability without changing any functionality.
110-114: Task List Checked State Styling
The style changes for checked task list items (lines 110–114) are purely cosmetic and continue to provide clear visual feedback.
172-191: Updated Heading Sizes for Consistency
Adjusting the font sizes for headings (h1–h3; lines 172–191) ensures a consistent typographic scale throughout the document.
194-197: Disable List Item Placeholder
Introducingcontent: none !important;(lines 194–197) effectively disables the placeholder in list items and is a clear, intentional styling update.
216-225: Adjusted Margins and Paragraph Spacing
Reducing the margin and line-height for list items (lines 216–220) as well as paragraphs (lines 221–225) creates a cleaner, more compact layout.apps/mail/components/ui/resizable.tsx (2)
27-33: Reordered Class Names in ResizableHandle
In theResizableHandlecomponent (line 29), moving the"bg-border"class to the beginning helps ensure consistent styling order. No functional changes are introduced.
34-38: Consistent Border Styling for Handle
Reordering the innerdiv’s class names (line 35) so that"bg-border"leads the list is a purely cosmetic change that increases clarity.apps/mail/app/page.tsx (3)
3-6: Updated Imports for Consistency
The addition of theSkeleton(and reordering withHero) import (lines 3–6) ensures that all necessary components are loaded consistently and improves code clarity.
12-14: Consistent Gradient Background Styling
The reordering of class names in the gradient background div (line 13) does not alter functionality but contributes to a uniform and easily readable styling format.
16-18: Refined Suspense Structure
Moving the<Navbar />inside the<Suspense>fallback (lines 16–18) makes the code structure clearer. This is a formatting adjustment only..github/CONTRIBUTING.md (1)
1-255: Improved Markdown Formatting
The insertion of blank lines and spacing adjustments throughout.github/CONTRIBUTING.mdenhances readability and structure without affecting any content. The changes are beneficial for long-term maintainability of our docs.🧰 Tools
🪛 LanguageTool
[uncategorized] ~78-~78: Possible missing preposition found.
Context: ...clear, descriptive commit messages - Reference issues and pull requests ```bash ...(AI_HYDRA_LEO_MISSING_TO)
[uncategorized] ~170-~170: Possible missing preposition found.
Context: ...ict"no-explicit-any"in the future - Ensure all code passes type checking, as build...(AI_HYDRA_LEO_MISSING_TO)
🪛 markdownlint-cli2 (0.17.2)
143-143: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
apps/mail/components/ui/chart.tsx (5)
52-57: Optimized ChartContainer Styling
In theChartContainercomponent (lines 52–57), reordering the CSS classes refines readability while maintaining identical visual results.
136-138: Concise Conditional Assignment
Reformatting the assignment ofvalue(line 137) into a single, clear line improves code clarity without changing its behavior.
161-165: Enhanced Tooltip Styling
The reordering of class names in the tooltip container (lines 161–165) leads to a cleaner CSS structure while keeping consistent styling.
269-273: Reordered Legend Item Classes
Adjusting the class name order for legend items (lines 269–273) creates uniformity with other components. This cosmetic change makes the styling easier to maintain.
1-328: Overall Chart Component Styling
Across theChartContainer,ChartTooltipContent, andChartLegendContentcomponents, the comprehensive reordering and reformatting of class names are purely cosmetic. These changes, introduced by Prettier, standardize our code style across the chart components without impacting functionality.🧰 Tools
🪛 Biome (1.9.4)
[error] 75-75: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
apps/mail/components/create/editor.node-selector.tsx (2)
104-105: Cosmetic Class Name Reordering in PopoverTriggerThe class names for the
<PopoverTrigger>component have been reordered so thathover:bg-accentappears first. This change is purely cosmetic and improves consistency with similar components throughout the codebase.
119-120: Cosmetic Class Name Reordering in EditorBubbleItemThe class names for the
<EditorBubbleItem>have been reordered (withhover:bg-accentnow at the beginning) to enhance readability without impacting functionality.apps/mail/app/(full-width)/contributors/page.tsx (3)
26-27: Reordered Imports for ConsistencyThe imports for
ThemeToggleand the social icons (Discord,
136-140: Ternary Operator Formatting in SWR HookThe ternary expression for determining the URL for additional contributors has been reformatted (with line breaks added) to improve readability. There is no change in behavior—this is a straightforward cosmetic improvement.
819-825: Improved Formatting in Custom XAxis Tick RendererThe inline arrow function within the custom tick renderer (for the
<XAxis>) has been reformatted. The change makes it easier to read the process of finding the contributor usingallContributors?.find(...)without affecting functionality.apps/mail/components/home/hero.tsx (4)
87-89: Cosmetic Formatting of HeadlineThe
<p>element for the headline has been reformatted (with reordered class names and adjusted spacing) for better clarity. This change is purely stylistic and does not modify any functionality.
90-94: Balanced Component FormattingThe
<Balancer>component now has itsclassNamereordered (e.g. placingdark:text-shinyGrayearly in the string). This improves readability and maintains consistency, with no impact on how the component renders.
101-107: Cosmetic Success Message FormattingThe success branch (rendering the waitlist confirmation) has been reformatted, including the reordering of class names and adjustments in text indentation. These refinements are cosmetic only and keep the intended UI behavior intact.
110-124: Formatting Improvements in Button with ImageThe
<Button>component’s class list and the nested<Image>element have been reformatted. Changes such as reordering hover states and properly aligning the<Image>attributes enhance readability without affecting operation.apps/mail/components/create/ai-textarea.tsx (2)
1-5: Updated Import and Interface FormattingThe import statements (using a semicolon) and the single-line formatting of the interface declaration have been standardized using prettier. These modifications are strictly stylistic and do not affect functionality.
10-15: Improved Class Name Ordering in TextareaThe call to the
cnutility now lists the base classes and the dynamicclassNamein a consistent order. This reordering makes the styling easier to read and maintain while leaving the element’s appearance unchanged.apps/mail/lib/auth-providers.ts (4)
19-27: Consistent Formatting in Custom Providers ConfigurationIn the
customProvidersarray, thecustomRedirectPathproperty now includes a trailing comma and has been reformatted to a single-line style. This consistency improves readability without any impact on provider behavior.
29-52: Cosmetic Reformatting in Google Provider ConfigurationThe Google provider’s configuration has been reformatted:
- The
requiredEnvVarsarray is now a single-line array.- The
envVarInfoobjects have been adjusted for improved spacing and include trailing commas.
These changes are purely for clarity and maintain no functional differences.
53-70: Cosmetic Reformatting in GitHub Provider ConfigurationSimilarly, the GitHub provider’s settings (including
requiredEnvVarsandenvVarInfo) have been reformatted. The consistent layout and inclusion of trailing commas help with maintainability while not affecting execution.
73-87: Improved Formatting in Error Handling FunctionsThe error logging within the
isProviderEnabledandgetSocialProvidersfunctions now uses consistent arrow function syntax and trailing commas where appropriate. These changes enhance code readability and help standardize logging output while preserving the current logic.apps/mail/instrumentation.ts (1)
1-1: Consistent quote style applied.The changes in this file standardize the use of double quotes instead of single quotes for string literals, which aligns with Prettier's default configuration.
Also applies to: 4-5, 8-9
apps/mail/components/create/selectors/node-selector.tsx (4)
12-19: Formatting standardized for imports and component structure.Quotes have been standardized to double quotes and semicolons have been properly added at the end of statements.
20-25: Type definition formatted with consistent semicolons.The
SelectorItemtype definition now consistently uses semicolons at the end of each property declaration.
29-87: Array items formatting standardized.The formatting of the
itemsarray has been standardized with consistent use of:
- Double quotes for string literals
- Arrow function syntax for methods
- Semicolons at the end of statements
89-92: Component structure and JSX attributes standardized.The
NodeSelectorcomponent's formatting has been standardized with:
- Consistent class name ordering (utility classes first)
- Proper indentation and spacing
- Arrow function syntax for callbacks
Also applies to: 94-133
apps/mail/components/create/selectors/link-selector.tsx (4)
1-8: Import statements standardized with double quotes.Import statements have been reformatted to consistently use double quotes and proper semicolons.
10-26: Helper functions formatted with consistent semicolons.The
isValidUrlandgetUrlFromStringfunctions have been updated with proper semicolons at the end of return statements.
33-40: Component initialization formatted with proper semicolons.The hook initializations and
useEffecthave been properly terminated with semicolons.
46-56: JSX structure standardized with consistent formatting.The formatting of JSX elements has been standardized with:
- Consistent class name ordering
- Proper indentation
- Use of double quotes for attributes
- Semicolons after function calls
Also applies to: 57-102
apps/mail/components/create/editor.colors.tsx (1)
129-129: Class name ordering standardized.The class names have been reordered to follow a consistent pattern, with utility classes like
text-muted-foregroundandhover:bg-accentappearing first in the list.Also applies to: 142-142, 154-154, 162-162
apps/mail/app/(auth)/login/page.tsx (3)
2-2: Import order and string literal formatting standardized.Import statements have been reordered and string literals now consistently use double quotes.
Also applies to: 6-6
8-15: Arrow function syntax standardized with consistent parentheses.Arrow functions now consistently use parentheses around parameters and proper trailing commas in objects.
Also applies to: 27-35
41-41: Class name ordering standardized.Class names have been reordered to follow a consistent pattern, with layout utilities like
min-h-screenappearing before sizing utilities likew-full.apps/mail/app/globals.css (8)
105-107: Improved Tailwind Directive Formatting in Body Selector
The reordering and formatting of the@apply bg-background text-foreground font-sans;statement improves readability without affecting functionality.
116-118: Enhanced Skeleton Text Block Formatting
The updated formatting for the selector (using@apply bg-foreground/20 animate-pulse select-none rounded-md;) makes the intent clearer while preserving the visual result.
125-126: Consistent Skeleton Div Formatting
The reordering of classes in the.skeleton-divselector is purely cosmetic and improves consistency across similar components.
205-211: Multi-line Formatting for Compose Gradient Background
Reformatting thebackground: linear-gradient(...)in the.compose-gradientclass into a multi-line style enhances clarity and maintainability without changing the gradient values.
217-223: Refined Gradient Animated Background and Box-Shadow Formatting
Splitting the background declaration and box-shadow properties over multiple lines (in.compose-gradient-animated) improves readability. No functional changes are introduced.Also applies to: 226-229
232-242: Clearer Keyframes Definition for Gradient Animation
The updated multi-line keyframe definitions forgradient-animationnow present a cleaner, more maintainable format while preserving all animation properties.
299-305: Consistent Pseudo-element Styling for Scrollbar Hiding
Reformatting the hide-scrollbar rules (for IE, Firefox, and Webkit) provides uniformity in style declaration, with no impact on behavior.
327-334: Improved Blink Keyframes Readability
Breaking the@keyframes blinkinto clearly separated steps enhances readability without modifying its intended animation effect.apps/mail/components/create/slash-command.tsx (2)
13-16: Standardized Import Order and String Delimiter Usage
The consolidation of import statements—such as moving theYoutubeimport into the grouped list—and use of double quotes improves import consistency.
19-28: Consistent Formatting in Suggestion Items Definition
The formatting adjustments (including consistent quotation marks and inline method calls) within thesuggestionItemsarray enhance readability while leaving functionality unchanged.apps/mail/components/home/footer.tsx (3)
3-6: Reordered Component Imports for Clarity
Reordering the imports (movingDiscordandGithuband positioningLinkappropriately) makes the file structure more intuitive without altering behavior.
9-27: Cosmetic Improvements in Social Links Configuration
Adding trailing commas and updating values (e.g., updating Twitter’s ariaLabel to "X (Twitter)") standardizes the object structure. These changes are purely stylistic.
29-88: Refined JSX Structure in Footer Component
Reordering class names and adjusting spacing in the JSX improves readability and consistency in theFootercomponent while leaving the rendered output unchanged.apps/mail/components/create/extensions.ts (8)
1-22: Enhanced Import Consistency and Inclusion of New Modules
The import block now uses double quotes uniformly and includes the newly addedMathematicsmodule, which improves consistency and maintainability without impacting functionality.
23-27: Additional Import for UploadImagesPlugin
Introducing the import forUploadImagesPluginfrom "novel" follows the same formatting conventions, contributing to overall codebase consistency.
29-47: Uniform Configuration for Tiptap Extensions
The reformatting of variable assignments (e.g.,aiHighlight,placeholder) and the configuration of extensions likeTiptapLinkusing consistent indentation and semicolon usage improves readability while preserving original behavior.
55-90: Consistent Formatting in Image, List, and Block Configurations
Adjustments in the configuration blocks fortiptapImage,updatedImage,taskList, and related components enhance clarity through uniform use of class names and spacing.
120-131: Refined Lowlight and CodeBlock Configuration
The configuration forcodeBlockLowlightnow cleanly integrates thecreateLowlightfunction and adds clarifying comments, ensuring easier maintenance.
126-138: Neat Formatting for Media Extensions
The multi-line formatting adjustments foryoutubeandinline: falseproperty) streamline the code’s appearance without functional impact.
140-147: Readable Mathematics Extension Setup
Reformatting themathematicsextension configuration (including class names and katex options) improves its legibility, making future adjustments easier while maintaining intended functionality.
149-172: Consistent Semicolon Usage in Exports Array
The export arraydefaultExtensionsnow adheres to a standardized format, including semicolon placement and line breaks that enhance overall clarity without altering behavior.apps/mail/components/ui/command.tsx (7)
17-20: Reordered Utility Classes in Command Component
The update to theCommandcomponent’s className (now starting withbg-popover text-popover-foreground) maintains all styling while offering a more logical grouping of utility classes for improved readability.
31-33: Concise Class Name Adjustments in CommandDialog
The reordering within theCommandDialogcomponent’s<Command>element further clarifies the styling intent (with focused adjustments to group headings and item paddings), leaving functionality unaffected.
44-46: Improved Structure in CommandInput Component
Reordering of the container’s class names and the inclusion of the search icon (with updated utility classes) enhance readability and maintain a consistent visual style.
87-90: Enhanced Group Styling in CommandGroup Component
The updated class order in theCommandGroupcomponent (placingtext-foregroundat the forefront) offers clearer visual priority with no change to functionality.
101-105: Streamlined Separator Styling
Reordering the class names for theCommandSeparator(e.g.,bg-border -mx-1 h-px) offers a cleaner and more consistent appearance across the UI components.
115-120: Refined Item Styling for CommandItem
Moving the selected-item modifiers (data-[selected=true]:bg-accent data-[selected=true]:text-accent-foreground) to the start of the class list improves clarity without affecting the interaction styling.
128-132: Clear and Consistent Shortcut Styling
The updated class order in theCommandShortcutcomponent (withborder-border bg-backgroundnow prioritized) enhances readability and preserves the component’s functionality.apps/mail/components/context/thread-context.tsx (1)
1-294: LGTM - Code formatting changes look goodThe code changes are purely formatting improvements from running Prettier, including reorganized imports, consistent indentation, and better spacing. No functional changes were made.
apps/mail/components/icons/animated/settings-lines.tsx (1)
58-58: Formatting change approvedThis is a simple reordering of class names in the className attribute, moving "hover:bg-accent" from the beginning to the end of the class list. No functional change.
apps/mail/components/icons/animated/message.tsx (1)
73-73: Formatting change approvedThis is a simple reordering of class names in the className attribute, moving "hover:bg-accent" from the beginning to the end of the class list. No functional change.
apps/mail/components/icons/animated/users.tsx (1)
71-71: Formatting change approvedThis is a simple reordering of class names in the className attribute, moving "hover:bg-accent" from the beginning to the end of the class list. No functional change.
apps/mail/components/icons/animated/shield.tsx (1)
72-76: Cosmetic Class Reordering in ShieldCheckIcon
The reordering of the Tailwind CSS classes in theclassNameattribute (movinghover:bg-accentwithin the list) is purely cosmetic and improves consistency across components. No functionality is affected.apps/mail/components/icons/animated/moon.tsx (1)
64-68: Cosmetic Update for MoonIcon
The change reorders the Tailwind CSS classes in theclassNameattribute of the main<div>, aligning it with other icon components. This adjustment is purely stylistic and maintains intended behavior.apps/mail/components/icons/animated/archive.tsx (1)
82-86: Standardizing Class Order in ArchiveIcon
The update moves thehover:bg-accentclass within the class list to ensure a consistent coding style across components. This cosmetic change does not affect the functionality of the component.apps/mail/components/icons/animated/x.tsx (1)
61-65: Consistent Class Name Arrangement in XIcon
The reordering of classes in theclassNameattribute maintains consistency with the updated style guidelines. This formatting change is purely cosmetic and preserves the component's functionality.apps/mail/components/icons/animated/check-check.tsx (1)
73-77: Cosmetic Class Reordering in CheckCheckIcon
The adjustment to theclassNameorder (relocatinghover:bg-accent) is a stylistic improvement aimed at consistency across the codebase. There are no functional changes introduced by this update.apps/mail/components/ui/separator.tsx (1)
16-17: Cosmetic Update: Class Name Reordering
The class names have been reordered from"shrink-0 bg-border"to"bg-border shrink-0". This change is purely cosmetic and improves consistency across the codebase without affecting functionality.apps/mail/components/icons/animated/book-text.tsx (1)
48-50: Cosmetic Update: Standardizing Class Name Order
The updated className string reorders the utility classes to maintain uniformity with other icon components. This change does not alter behavior but enhances readability and consistency.apps/mail/components/icons/animated/arrow-left.tsx (1)
70-72: Cosmetic Update: Consistent Class Name Order
The reordering of class names in the<div>(shifting the placement of"hover:bg-accent") is a formatting improvement that maintains functional parity while standardizing style across components.apps/mail/components/icons/animated/settings-gear.tsx (1)
51-52: Cosmetic Update: Class Name Ordering Consistency
This update reorders the classes within theclassNameattribute simply for consistency with the broader code style guidelines enforced by prettier—no functional changes are present.apps/mail/components/icons/animated/align-vertical.tsx (1)
80-81: Cosmetic Update: Unified Class Name Format
The modification reorders the class names to align with the standardized approach used across similar components. This is a cosmetic adjustment aimed at improving code readability and consistency.apps/mail/components/icons/animated/inbox.tsx (1)
65-65: Cosmetic Change: Reordered CSS classes for consistency.The updated class order in the
<div>element aligns with the Prettier formatting rules and maintains the same visual styling and functionality.apps/mail/app/(routes)/create/page.tsx (1)
5-6: Cosmetic Update: Adjusted CSS Class Order.Reordering the class names in both the outer (
<div className="flex h-full w-full flex-col">) and inner (<div className="h-full flex-1">) containers improves consistency with similar components. These changes are purely cosmetic and do not impact the layout or functionality.apps/mail/components/icons/animated/cart.tsx (1)
63-63: Cosmetic Change: Updated CSS Class Ordering.The adjustment in the order of CSS classes in the
<div>element is a formatting change only. This does not affect the behavior of the component but enhances the overall code consistency.apps/mail/app/(routes)/mail/under-construction/[path]/page.tsx (1)
26-26: Cosmetic Update: Reordered Class Names.The new class name order in the
<Construction>component (i.e."text-muted-foreground h-16 w-16 animate-pulse") improves readability while retaining the same styling and functionality.apps/mail/app/(routes)/create/layout.tsx (1)
7-7: Cosmetic Change: Adjusted Class Name Ordering.Reordering the class names in the
<div>element to"w-full bg-white md:p-3 dark:bg-black"enhances consistency across the codebase. The change is purely cosmetic and does not alter the component's layout or behavior.apps/mail/components/icons/animated/sparkles.tsx (1)
91-98: Cosmetic CSS Class Reordering in SparklesIcon
The updated ordering of Tailwind CSS classes in the<div>(e.g. movinghover:bg-accentcloser to the other positioning classes) improves readability and consistency. This change is purely cosmetic and does not impact functionality.apps/mail/components/icons/animated/keyboard.tsx (1)
84-90: Reordered CSS Classes in KeyboardIcon
The reordering of the class names—placinghover:bg-accentat the start of the class list—enhances consistency with the project's updated styling conventions. No functional changes are introduced.apps/mail/components/mail/mail-display.tsx (1)
8-8: Reorganized Import Statements
Moving theParsedMessageimport to a new position clarifies the import order and aligns with our formatting guidelines. This is a purely cosmetic change with no functional impact.apps/mail/components/icons/animated/search.tsx (1)
48-55: Consistent Class Name Ordering in SearchIcon
The adjustment in the ordering of the Tailwind CSS classes in the container<div>is a cosmetic update aimed at improving the consistency and readability of the styling.apps/mail/components/icons/animated/filter.tsx (1)
62-68: Standardized CSS Class Ordering in FilterListIcon
Reordering the class names (withhover:bg-accentnow at the beginning) aligns this component with the overall styling conventions. It’s a purely cosmetic change that maintains the component's functionality.apps/mail/components/mail/mail.tsx (1)
14-14: Import Reordering:
Theimport type { MessageKey } from "@/config/navigation";statement has been moved to a new position in the import group. This reordering is purely cosmetic and helps maintain a consistent and organized import order across the file.apps/mail/actions/mail.ts (1)
25-25: Semicolon Consistency in Error Handling:
Across multiple catch blocks (ingetMails,getMail,markAsRead,markAsUnread,mailCount, andmodifyLabels), semicolons have now been added after theawait deleteActiveConnection()calls. This change is stylistic only and improves code consistency without altering the underlying error-handling logic.Also applies to: 39-39, 51-51, 63-63, 74-74, 109-109
apps/mail/app/(routes)/mail/create/page.tsx (1)
5-6: Class Name Reordering for Layout Consistency:
The changes to the class names on the outer and inner<div>elements—switching to"flex h-full w-full flex-col"and"h-full flex-1"respectively—are purely cosmetic. They improve readability and maintain a standardized order of utility classes without affecting the component's layout.apps/mail/components/icons/animated/trash.tsx (1)
62-62: ClassName Order Standardization:
Reordering the classes on the<div>(placinghover:bg-accentat the beginning) does not change the rendered output but enhances readability and consistency across the codebase. This type of adjustment aligns with the overall Prettier reformatting effort.apps/mail/app/error.tsx (2)
12-13: Outer Container Class Ordering:
The updated order of class names in the outer<div>("dark:bg-background flex w-full items-center justify-center bg-white text-center") helps standardize styling conventions without impacting functionality. This change is purely cosmetic.
22-22: Button Class Name Reordering:
The reordering of class names on the<Button>component (now"text-muted-foreground gap-2") improves consistency with similar components across the application. This adjustment is cosmetic and does not affect behavior.apps/mail/components/ui/card.tsx (2)
9-11: Reordering of CSS Classes in the Card ComponentThe CSS classes in the
Cardcomponent have been reordered to"bg-card text-card-foreground rounded-lg border shadow-sm". This is a purely cosmetic change that improves consistency and readability without affecting functionality.
34-38: Reordering of CSS Classes in the CardDescription ComponentThe className string has been updated from
"text-sm text-muted-foreground"to"text-muted-foreground text-sm". This change is cosmetic and helps maintain a consistent class order across components.apps/mail/components/icons/animated/sun.tsx (1)
57-60: Reordering of CSS Classes in the SunIcon ComponentThe
<div>element’s className has been updated by moving"hover:bg-accent"to the beginning of the class string. This cosmetic adjustment aligns the component’s styling with similar components for better consistency.apps/mail/components/icons/animated/square-pen.tsx (1)
65-70: Consistent CSS Class Order in the SquarePenIcon ComponentThe className now starts with
"hover:bg-accent/10", ensuring a consistent ordering of classes similar to other icon components. This is solely a cosmetic update and does not alter the component’s functionality.apps/mail/components/ui/button.tsx (1)
20-22: Improved Readability of DropdownItem VariantThe
dropdownItemvariant withinbuttonVariantshas been reformatted from a single-line declaration to a multi-line format. This enhances readability and maintainability without changing the applied CSS classes.apps/mail/components/icons/animated/bell.tsx (1)
54-59: CSS Class Order Adjustment in the BellIcon ComponentThe
classNamefor the<div>in theBellIconcomponent has been updated to position"hover:bg-accent"at the beginning. This cosmetic change aligns the styling with other similar components and does not affect its behavior.apps/mail/components/ui/tabs.tsx (3)
17-17: CSS class reordering by PrettierThe CSS class names in the
TabsListcomponent'sclassNamehave been reordered by Prettier, maintaining the same classes but with "bg-muted text-muted-foreground" now appearing at the beginning.
32-32: CSS class reordering by PrettierThe CSS class names in the
TabsTriggercomponent'sclassNamehave been reordered by Prettier, with "ring-offset-background" now positioned at the beginning.
47-47: CSS class reordering by PrettierThe CSS class names in the
TabsContentcomponent'sclassNamehave been reordered by Prettier, with "ring-offset-background" now positioned at the beginning.apps/mail/actions/connections.ts (1)
4-4: Import statement reformattedThe import statement for
IConnectionhas been reformatted by Prettier, maintaining the same functionality.apps/mail/actions/extractText.ts (3)
2-2: String delimiter standardizationChanged single quotes to double quotes in the cheerio import statement as part of Prettier formatting.
10-11: String delimiter standardizationChanged single quotes to double quotes in the selector strings for removing script and style elements.
14-14: String delimiter standardizationChanged single quotes to double quotes in the body selector and string replacements for text cleaning.
Also applies to: 16-17
apps/mail/components/icons/animated/expand.tsx (8)
1-7: String delimiter standardizationChanged single quotes to double quotes in the client directive and import statements.
19-19: String delimiter standardizationChanged single quotes to double quotes in the type property of defaultTransition object.
33-34: String delimiter standardizationChanged single quotes to double quotes in the animation control method strings.
41-42: String delimiter standardization and dependency array formattingChanged single quotes to double quotes in the animation state and formatted the dependency array.
Also applies to: 46-46
52-53: String delimiter standardization and dependency array formattingChanged single quotes to double quotes in the animation state and formatted the dependency array.
Also applies to: 57-57
63-65: CSS class reordering by PrettierThe CSS class string and className property have been reformatted with proper indentation.
85-87: String delimiter standardization in animation variantsChanged single quotes to double quotes in all the animation variant properties.
Also applies to: 94-96, 103-105, 112-114
120-123: Component formatting and string delimiter standardizationChanged the formatting of the component closing and the string delimiter in the displayName property.
apps/mail/components/icons/icons.tsx (1)
33-36: Cosmetic Formatting in the Discord Icon SVG
The<path>element for the Discord icon has been reformatted into a multi-line structure with adjusted indentation. This change is purely cosmetic and does not modify the icon’s appearance or functionality.apps/mail/actions/brain.ts (2)
1-7: Reordered Imports for Enhanced Readability
The import statements have been reordered—placing framework and utility imports before theauthanddbmodules—to improve consistency and readability. This adjustment is purely stylistic.
9-30: Consistent Indentation in the EnableBrain Function
The body of theEnableBrainfunction has been reformatted with consistent two-space indentation. This cleanup improves the readability of the logic (e.g., session validation and axios request) while preserving the original functionality.apps/mail/components/create/editor.link-selector.tsx (2)
6-6: Restored React Hooks Imports
The reintroduction ofuseEffectanduseReffrom React is essential for managing side effects and element references in this component. Their restoration aligns the file with previous usage patterns and ensures correct functionality.
72-73: Adjusted Class Name Order on Input Element
The order of classes on the input element has been changed (from"flex-1 bg-background p-1 text-sm outline-none"to"bg-background flex-1 p-1 text-sm outline-none"). This reordering is purely cosmetic and does not affect the styling or behavior.apps/mail/app/(auth)/zero/signup/page.tsx (2)
29-31: Consistent Email Suffix Application
The interpolation of the@0.emailsuffix in the email assignment is correctly implemented. This change maintains consistency with the intended user format and does not alter the functional flow.
123-140: Footer Markup Reformatting for Consistency
The footer’s markup—spanning the container div and anchor elements—has been reformatted, including reordering of class names. These adjustments improve layout consistency and readability without impacting any functionality.apps/mail/components/ui/accordion.tsx (4)
1-8: Improved Import Order and Client Directive Placement
The updates include placing the"use client"directive at the top and reordering the import statements. This standardized order boosts clarity and aligns with overall project conventions.
15-18: Standardized Display Name Assignment in AccordionItem
TheAccordionItemcomponent now assigns itsdisplayNamewith a semicolon, following a consistent pattern. This is a minor stylistic improvement with no impact on functionality.
26-37: Consistent Formatting in AccordionTrigger
The class name concatenation anddisplayNameassignment for theAccordionTriggercomponent have been reformatted to align with the project’s style guidelines. These changes are cosmetic and preserve the component’s intended behavior.
43-55: Cleaned-Up Formatting for AccordionContent
Reformatting in theAccordionContentcomponent, such as the explicit animation class names and spacing utilities, enhances readability. The behavior and functionality remain intact.apps/mail/components/ui/drawer.tsx (2)
44-44: Class names reordering looks goodThe reordering of class names is consistent with running Prettier on the codebase. This is a purely cosmetic change that doesn't affect functionality.
79-79: Consistent class name reorderingThe reordering of class names from
"text-sm text-muted-foreground"to"text-muted-foreground text-sm"is in line with the standardization of class ordering through Prettier.apps/mail/app/(auth)/zero/login/page.tsx (4)
37-37: Class names reordering looks goodThe reordering of animation classes to appear before sizing classes is a cosmetic improvement that follows consistent formatting.
40-42: Improved text formattingBreaking the paragraph text into multiple lines improves readability while maintaining the same rendered output.
105-107: Footer formatting looks goodThe footer div class ordering and spacing has been standardized, which improves consistency throughout the codebase.
108-116: Link class standardizationThe link classes have been consistently reordered across both footer links, maintaining the same styling while improving code consistency.
apps/mail/actions/getSummary.ts (2)
1-6: Improved import organizationThe "use server" directive is now consistently formatted, and imports have been reordered logically. This enhances code readability without changing functionality.
9-35: Consistent indentation throughout functionThe function body now has consistent indentation, making the code structure more readable while preserving the original logic.
apps/mail/components/mail/navbar.tsx (2)
46-46: Class name ordering standardizedThe reordering of utility classes from
"ml-auto text-muted-foreground"to"text-muted-foreground ml-auto"follows a consistent pattern of putting color-related classes before positioning classes.
56-56: Consistent dark mode class orderingDark mode related classes have been reordered to group background classes followed by text classes, improving code consistency without changing the rendered result.
apps/mail/components/create/editor-buttons.tsx (8)
1-2: Code formatting looks goodThese import statements have been formatted using double quotes for consistency.
5-8: Clean formatting with semicolonsThe useCurrentEditor hook usage and return statement now have proper semicolons for consistent syntax.
16-17: Improved button properties formattingThe button properties (disabled and className) have been simplified to single-line expressions and use consistent double quotes, improving readability.
Also applies to: 23-24, 30-31, 37-38
42-43: Consistent button formattingThe Clear marks/nodes buttons are now consistently formatted on single lines with proper semicolons.
46-46: Consistent className formattingThe className attributes for paragraph, headings, and list buttons now use double quotes consistently.
Also applies to: 52-52, 58-58, 64-64, 70-70, 76-76, 82-82, 88-88, 94-94, 100-100, 106-106
113-113: Button formatting consistencyThe hard break button and undo/redo button properties now follow the same formatting pattern as other buttons.
Also applies to: 116-116, 122-122
127-128: Color button property formattingThe color button properties are now consistently formatted with the rest of the component.
134-135: Clean export formattingThe component return statement and export default now have proper semicolons and consistent formatting.
Also applies to: 138-139
apps/mail/actions/utils.ts (4)
2-3: Reorganized imports for readabilityThe imports have been reordered in a logical way with the connection import first, followed by revalidatePath.
9-9: Consistent string quotesFatalErrors array now uses double quotes instead of single quotes for consistency.
11-29: Improved function formattingThe deleteActiveConnection function has been reformatted with consistent spacing and indentation, making it more readable while maintaining the same functionality.
31-61: Consistent getActiveDriver formattingThe getActiveDriver function has been reformatted with proper spacing, indentation, and blank lines for improved readability.
apps/mail/components/create/editor-menu.tsx (5)
1-4: Consistent import formattingImport statements now use double quotes and the ReactNode type is properly imported.
7-9: Interface property formattingEditorMenuProps interface properties now have semicolons for TypeScript consistency.
12-13: Consistent function parameter formattingThe function parameter destructuring and useEditor hook now have proper semicolons.
16-18: useEffect formattingThe useEffect hook return statements now have proper semicolons for consistent syntax.
23-27: Consistent JSX formattingThe tippyOptions placement, onOpenChange callbacks, and className attributes are now consistently formatted with proper semicolons.
Also applies to: 29-29, 33-33
apps/mail/components/mail/mail-compose.tsx (7)
24-24: Uncommented sendEmail importThe sendEmail import has been explicitly added for clarity.
145-145: Consistent FileIcon className orderingThe FileIcon className attributes have been reordered with "text-primary" following the sizing classes.
Also applies to: 231-231
151-151: Consistent text element formattingThe text elements' className attributes have been reordered with text modifiers first.
Also applies to: 154-154, 237-237, 240-240
166-166: Consistent Badge className orderingThe Badge className has been reordered with hover states following the primary classes.
198-198: Consistent hover className placementThe hover:bg-muted class has been moved to the beginning of the className for consistency.
262-262: Consistent Card className formattingThe Card className has been reordered with background classes first.
279-279: Consistent list className formattingThe dropdown list className attributes have been reordered consistently.
Also applies to: 287-287
apps/mail/app/(auth)/login/login-client.tsx (12)
5-6: Reorganized importsReact hooks and EnvVarInfo imports have been reordered for better organization.
51-51: Consistent image classNameThe image className has been reordered to follow the project's className ordering convention.
65-75: Consistent arrow function syntaxThe filter and map operations now use consistent arrow function syntax for improved readability.
Also applies to: 77-83
86-89: Cleaner state update syntaxThe toggleProvider function now uses a cleaner arrow function for state updates.
100-100: Consistent spacing and line breaksAdded appropriate line spacing between different logical sections of the code.
Also applies to: 105-105, 129-129
135-138: Consistent container className formattingThe main container and header div className attributes have been reordered following utility-first CSS conventions.
Also applies to: 148-152
154-154: Consistent UI element classNamesThe className attributes across various UI elements (alerts, buttons, status indicators) have been reordered for consistency.
Also applies to: 188-195, 207-207, 221-224, 226-237, 240-247, 270-270, 293-293
177-184: Clean JSX text formattingThe JSX text content has been cleaned up with consistent spacing and string interpolation.
273-285: Consistent SVG formattingThe SVG element and its attributes are now consistently formatted.
318-330: Consistent function mapping syntaxThe provider mapping function now uses consistent arrow function syntax with explicit return.
335-347: Clean footer formattingThe footer and its links now have consistently ordered className attributes.
354-354: Added missing semicolonAdded semicolon to the end of the component for consistency.
apps/mail/components/icons/animated/more-vertical.tsx (1)
1-108: Code formatting changes look good.The changes in this file are purely formatting-related, adding semicolons at the end of statements and reordering class names in the className property. These changes align with the PR objective of running Prettier on the codebase and improve code style consistency.
apps/mail/components/mail/search-bar.tsx (9)
8-9: Import and variable declarations properly formatted.The reordering of imports and addition of proper spacing between variable declarations improves code readability and consistency.
Also applies to: 12-17
121-126: Improved useMemo implementations with proper formatting.The reformatting of the useMemo hooks with consistent indentation and trailing commas improves code readability.
Also applies to: 128-138
140-205: handleInputChange function reformatted for better readability.The function has been properly formatted with consistent spacing, indentation, and semicolons, making the logic easier to follow.
207-281: handleKeyDown function reformatted with consistent style.The function has been restructured with proper indentation and spacing, improving code readability without changing functionality.
304-337: Callback functions properly formatted.The submitSearch, handleSuggestionClick, and handleDateSelect callback functions have been reformatted with consistent spacing and indentation, improving code readability.
Also applies to: 339-373, 375-426
451-457: UI component styling properly formatted.The className properties and style objects have been reformatted with consistent ordering and spacing, improving code organization.
Also applies to: 469-475
487-497: Button styling properly formatted.The className concatenation and event handlers have been reformatted with consistent indentation, improving code readability.
518-521: Keyboard shortcut UI properly formatted.The formatting of keyboard shortcut elements has been improved with consistent spacing and styling.
582-582: Consistent className formatting across UI components.The className properties across various UI components have been reformatted with consistent ordering of utility classes, improving code consistency.
Also applies to: 616-616, 729-730, 740-741, 751-752, 762-763, 778-778, 784-785
apps/mail/components/icons/animated/reply.tsx (1)
1-121: Code formatting changes look good.The changes in this file are purely formatting-related, adding semicolons at the end of statements and declarations, and reordering class names in the className property. These changes align with the PR objective of running Prettier on the codebase and improve code style consistency.
| </VisuallyHidden> | ||
| <DialogContent className="bordr-none w-full overflow-y-auto p-0 sm:max-w-lg [scrollbar-width:none] [-ms-overflow-style:none] [&::-webkit-scrollbar]:hidden"> | ||
| <DialogContent className="bordr-none w-full overflow-y-auto p-0 [-ms-overflow-style:none] [scrollbar-width:none] sm:max-w-lg [&::-webkit-scrollbar]:hidden"> | ||
| {children} |
There was a problem hiding this comment.
Potential Typo in DialogContent ClassName
The className string in the DialogContent component begins with "bordr-none", which appears to be a typo. It likely should be "border-none". Please verify and correct this to ensure the intended border style is applied.
Consider applying the following diff:
-<DialogContent className="bordr-none w-full overflow-y-auto p-0 ...
+<DialogContent className="border-none w-full overflow-y-auto p-0 ...📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| </VisuallyHidden> | |
| <DialogContent className="bordr-none w-full overflow-y-auto p-0 sm:max-w-lg [scrollbar-width:none] [-ms-overflow-style:none] [&::-webkit-scrollbar]:hidden"> | |
| <DialogContent className="bordr-none w-full overflow-y-auto p-0 [-ms-overflow-style:none] [scrollbar-width:none] sm:max-w-lg [&::-webkit-scrollbar]:hidden"> | |
| {children} | |
| </VisuallyHidden> | |
| <DialogContent className="border-none w-full overflow-y-auto p-0 [-ms-overflow-style:none] [scrollbar-width:none] sm:max-w-lg [&::-webkit-scrollbar]:hidden"> | |
| {children} |
|
jesus |
|
@MrgSub dont jesus me, it needed to be done |
|
LMAOO |
3 participants
Summary by CodeRabbit
All changes are cosmetic, streamlining internal organization and documentation without impacting the end-user experience.