Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(web): MobileAppBanner hydration error fix suggestion #17671

Merged
merged 4 commits into from
Jan 30, 2025

Conversation

thorkellmani
Copy link
Member

@thorkellmani thorkellmani commented Jan 27, 2025

What

  • Hydration error

local run on main branch
image

after pr changes
image

Still some issues but the hydration error is (mostly) gone

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • UI/UX Improvements
    • Enhanced mobile app banner visibility logic
    • Refined component rendering conditions to improve user experience
    • Optimized banner display mechanism based on mounting state

Copy link
Contributor

coderabbitai bot commented Jan 27, 2025

Walkthrough

The pull request modifies the MobileAppBanner component in the web application, focusing on refining the rendering and visibility logic. The primary change involves updating the condition for the Hidden component's screen prop to incorporate both the hidden state and the component's mounting status. This adjustment aims to provide more precise control over the banner's visibility, ensuring it remains hidden until fully mounted and when explicitly set to be hidden.

Changes

File Change Summary
apps/web/components/MobileAppBanner/MobileAppBanner.tsx - Modified Hidden component's screen prop condition
- Removed inline style for Box component
- Consolidated visibility logic

Possibly related PRs

Suggested Labels

deprecated:automerge

Suggested Reviewers

  • RunarVestmann
  • mannipje

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

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.

@thorkellmani thorkellmani marked this pull request as ready for review January 30, 2025 10:35
@thorkellmani thorkellmani requested review from a team as code owners January 30, 2025 10:35
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🔭 Outside diff range comments (1)
apps/web/components/MobileAppBanner/MobileAppBanner.tsx (1)

Line range hint 34-45: Improve platform detection to prevent potential hydration issues.

The getMobilePlatform function directly accesses browser APIs which could cause issues during server-side rendering. While the function checks for typeof navigator, it's better to encapsulate all browser-specific logic.

Consider this improved implementation:

-  const getMobilePlatform = (): string => {
-    if (typeof navigator === 'undefined') {
-      return ''
-    }
-    const userAgent = navigator.userAgent || navigator.vendor
-    return /iPad|iPhone|iPod/.test(userAgent) && !window.MSStream
-      ? 'apple'
-      : 'android'
-  }
+  const getMobilePlatform = (): string => {
+    if (typeof window === 'undefined') {
+      return ''
+    }
+    try {
+      const userAgent = window.navigator.userAgent || window.navigator.vendor
+      return /iPad|iPhone|iPod/.test(userAgent) && !window.MSStream
+        ? 'apple'
+        : 'android'
+    } catch {
+      return ''
+    }
+  }
🧹 Nitpick comments (3)
apps/web/components/MobileAppBanner/MobileAppBanner.tsx (3)

59-60: The hydration fix looks promising but could be further improved.

The change to include !isMounted in the Hidden component's screen prop helps prevent hydration mismatches by ensuring consistent server/client rendering. However, we could further optimize this to prevent any potential flash of content.

Consider this alternative approach:

-  return (
-    <Hidden screen={hidden || !isMounted} print={true}>
+  return (
+    <>
+      {/* Prevent hydration mismatch by deferring client-side rendering */}
+      {typeof window !== 'undefined' && (
+        <Hidden screen={hidden} print={true}>

This approach ensures the banner is only rendered client-side, completely eliminating the possibility of hydration mismatches.


Line range hint 15-19: Enhance type safety for browser APIs.

The current type declarations could be more specific to prevent potential type-related issues.

Consider these type improvements:

 declare global {
   interface Window {
-    MSStream: unknown
+    MSStream: boolean | undefined
+    navigator: Navigator & {
+      vendor: string
+    }
   }
 }

Line range hint 27-33: Optimize state management and initialization.

The component uses multiple state variables that could be consolidated, and the initialization logic could be improved.

Consider these improvements:

-  const [isMounted, setIsMounted] = useState(false)
-  const [hidden, setHidden] = useState<boolean>(
-    !!Cookies.get(COOKIE_NAME) || !appleLink || !androidLink,
-  )
-  const [isApple, setIsApple] = useState<boolean>(false)
+  interface BannerState {
+    isMounted: boolean;
+    hidden: boolean;
+    platform: 'apple' | 'android' | '';
+  }
+
+  const [bannerState, setBannerState] = useState<BannerState>(() => ({
+    isMounted: false,
+    hidden: !!Cookies.get(COOKIE_NAME) || !appleLink || !androidLink,
+    platform: '',
+  }));

This approach:

  • Consolidates related state
  • Uses a single state update
  • Makes the state structure more maintainable
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d46501c and dcdf55b.

📒 Files selected for processing (1)
  • apps/web/components/MobileAppBanner/MobileAppBanner.tsx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
apps/web/components/MobileAppBanner/MobileAppBanner.tsx (1)

Pattern apps/**/*: "Confirm that the code adheres to the following:

  • NextJS best practices, including file structure, API routes, and static generation methods.
  • Efficient state management and server-side rendering techniques.
  • Optimal use of TypeScript for component and utility type safety."

@thorkellmani thorkellmani added this pull request to the merge queue Jan 30, 2025
Merged via the queue into main with commit 2221053 Jan 30, 2025
28 checks passed
@thorkellmani thorkellmani deleted the fix/hydration branch January 30, 2025 10:55
thorhildurt pushed a commit that referenced this pull request Feb 3, 2025
* fix: init

* fix: more fix

---------

Co-authored-by: Jón Levy <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants