fix: (Fixes: #1430) make footer visible and responsive on all screen sizes

[Sompalkar]

Fixed footer disappearing and layout issues on screens smaller than 768px.
Changes include making the footer always visible, removing hidden opacity styles, improving layout with responsive flex direction, and adjusting spacing for better mobile readability.

Files affected:
components/home/footer.tsx

Tested across screen sizes — footer is now accessible and well-structured on both mobile and desktop.

Fixes: #1430

Summary by CodeRabbit

• Bug Fixes
  • Improved session validation across multiple components to prevent potential runtime errors and ensure actions only proceed when a valid user ID is present.
  • Enhanced footer layout and visibility for better responsiveness and consistent display on all screen sizes.
  • Fixed theme toggle in the user menu to clearly indicate the theme to switch to and added a keyboard shortcut hint.
  • Resolved potential errors when accessing user settings and color themes.
• Chores
  • Updated pre-commit hook for more reliable linting execution.
  • Adjusted command execution in the CLI to run within a shell environment for better compatibility.

[coderabbitai]

Walkthrough

This set of changes updates session property checks throughout the mail app to use safer optional chaining, preventing runtime errors if user objects are undefined. The footer component is refactored for improved responsiveness and visibility on small screens. Additional minor improvements are made to UI clarity and command execution safety.

Changes

File(s)	Change Summary
apps/mail/components/home/footer.tsx	Refactored footer for always-on visibility, improved responsive layout, and better display on small screens.
apps/mail/components/navigation.tsx apps/mail/components/pricing/comparision.tsx apps/mail/components/pricing/pricing-card.tsx apps/mail/hooks/use-drafts.ts apps/mail/hooks/use-settings.ts	Updated session checks to use session?.user?.id for safer access and error prevention.
apps/mail/components/ui/nav-user.tsx	Theme toggle now displays the opposite theme label and adds a shortcut hint; improved layout in dropdown.
apps/mail/providers/client-providers.tsx	Added optional chaining to safely access colorTheme from settings.
packages/cli/src/utils.ts	Added shell: true option to spawn in runCommand for shell environment execution.
.husky/pre-commit	Changed pre-commit hook to use npx pnpm lint-staged for more robust command resolution.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant FooterComponent
    participant Screen

    User->>Screen: Resize to < 768px
    Screen->>FooterComponent: Render
    FooterComponent-->>User: Footer remains visible with responsive layout

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Footer should be visible on smaller screens (#1430)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes detected.

Possibly related PRs

• Staging #1030: Both PRs modify session user ID checks in pricing-card.tsx, focusing on safer access and logic improvements.
• chore(ci): replace Bun with pnpm in Husky pre-commit hook #1202: Both PRs update the Husky pre-commit hook to alter how lint-staged is executed, ensuring proper command invocation.
• add bun back #1264: Both PRs adjust the pre-commit hook, though with different package manager commands, affecting the same workflow file.

Suggested reviewers

• ahmetskilinc
• MrgSub

Poem

In code’s bright meadow, a footer hops free,
No longer hidden, for all to see!
With safer checks and layouts spry,
The theme toggle winks a clever eye.
On every screen, both big and small—
This rabbit’s work delights them all!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a9be17b and 0e85b3f.

📒 Files selected for processing (2)

• apps/mail/components/ui/nav-user.tsx (2 hunks)
• apps/mail/providers/client-providers.tsx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• apps/mail/providers/client-providers.tsx
• apps/mail/components/ui/nav-user.tsx

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[MrgSub]

please resolve conflicts

[MrgSub]

Closing until conflicts are resolved