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: fixed logo refetch on re-render #2978

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

chesterkmr
Copy link
Collaborator

@chesterkmr chesterkmr commented Jan 20, 2025

Summary by CodeRabbit

  • Refactor
    • Updated internal logic for handling image loading in the Logo component to improve reference management.

Copy link

changeset-bot bot commented Jan 20, 2025

⚠️ No Changeset found

Latest commit: 200f15e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jan 20, 2025

Walkthrough

The pull request introduces a modification to the Logo component in the KYB application, focusing on improving the handling of the onLoad callback. A new hook useRefValue is utilized to create a reference that ensures the latest onLoad callback is used, preventing potential stale closure issues. The change aims to enhance the reliability of image loading and callback management within the component.

Changes

File Change Summary
apps/kyb-app/src/components/layouts/AppShell/Logo.tsx Introduced useRefValue hook to manage onLoad callback reference, updating useEffect dependency array and promise resolution

Poem

🐰 A Logo's Tale of Ref and Grace
Where closures once did stale embrace
A hook springs forth with nimble might
To keep callbacks fresh and bright
No more shall stale values hide
CodeRabbit's wisdom now resides! 🖼️


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.

CodeRabbit Configuration File (.coderabbit.yaml)

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

Documentation and Community

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

Copy link
Contributor

@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

🧹 Nitpick comments (1)
apps/kyb-app/src/components/layouts/AppShell/Logo.tsx (1)

28-28: Consider adding error handling for the image load.

The implementation correctly uses onLoadRef.current to avoid stale closures. However, you might want to consider handling potential image load failures explicitly.

-    Promise.race([prefetchImage(logoSrc), fallback(3000)]).then(onLoadRef.current);
+    Promise.race([prefetchImage(logoSrc), fallback(3000)])
+      .then(onLoadRef.current)
+      .catch(() => {
+        // Handle or log image load failures
+        onLoadRef.current?.();
+      });
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5ce73dc and 200f15e.

📒 Files selected for processing (1)
  • apps/kyb-app/src/components/layouts/AppShell/Logo.tsx (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: Analyze (javascript)
  • GitHub Check: test_windows
  • GitHub Check: test_linux
  • GitHub Check: build (windows-latest)
  • GitHub Check: lint
  • GitHub Check: build (ubuntu-latest)
🔇 Additional comments (3)
apps/kyb-app/src/components/layouts/AppShell/Logo.tsx (3)

1-1: LGTM! Good use of useRefValue hook.

Using useRefValue is a good practice here to prevent stale closure issues with the onLoad callback.

Also applies to: 20-21


29-29: LGTM! Correct dependency array update.

The dependency array correctly includes onLoadRef instead of onLoad, which is the right approach when using the ref value pattern.


Line range hint 1-32: Verify similar patterns in other components.

Let's check if there are other components that might benefit from the same fix.

✅ Verification successful

No changes needed in other components

The timeout pattern in the Logo component is specific to preventing UI locks in stepper breadcrumbs. Other image loading implementations serve different purposes where a timeout would be inappropriate:

  • Preload service requires actual load/error states for proper functionality
  • SVG to PNG converter needs successful image load to perform canvas operations
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for similar image loading patterns that might need the same fix
ast-grep --pattern 'new Image()' 

# Look for other Logo component usages
rg -l "Logo.*onLoad"

Length of output: 381


Script:

#!/bin/bash
# Check implementation of other files using new Image()
echo "=== preload-service/utils.ts ==="
rg -A 10 -B 5 "new Image\(\)" "sdks/web-ui-sdk/src/lib/services/preload-service/utils.ts"

echo -e "\n=== svg-to-png.ts ==="
rg -A 10 -B 5 "new Image\(\)" "apps/backoffice-v2/src/common/utils/svg-to-png/svg-to-png.ts"

Length of output: 1136

Promise.race([prefetchImage(logoSrc), fallback(3000)]).then(onLoad);
}, [logoSrc, onLoad]);
Promise.race([prefetchImage(logoSrc), fallback(3000)]).then(onLoadRef.current);
}, [logoSrc, onLoadRef]);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should this line be:

Suggested change
}, [logoSrc, onLoadRef]);
}, [logoSrc, onLoadRef.current]);

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Nope, it will trigger useEffect each time prop updates, that was the case of bug. So only using link to callback and not callback itself as dependency.

Comment on lines +28 to +29
Promise.race([prefetchImage(logoSrc), fallback(3000)]).then(onLoadRef.current);
}, [logoSrc, onLoadRef]);
Copy link
Collaborator

@ArtemLavrentii ArtemLavrentii Jan 20, 2025

Choose a reason for hiding this comment

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

@tomer-shvadron Wouldn't that bring back the bug ? I think best way to handle would be something like

Suggested change
Promise.race([prefetchImage(logoSrc), fallback(3000)]).then(onLoadRef.current);
}, [logoSrc, onLoadRef]);
Promise.race([prefetchImage(logoSrc), fallback(3000)]).then((value) => { if (onLoadRef.current) onLoadRef.current(value)) });
}, [logoSrc, onLoadRef]);

(cleanup is needed, just an idea suggestion)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Nope. It solves bug. Ref object is same each rerender whenever current is being updated. What you suggesting is pretty much safe check but its not needed in case withthen since it wont do anything if it will recieve undefined

Copy link
Collaborator

Choose a reason for hiding this comment

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

I was referring to proposed above changes in the first half :)

This isn't just a safe-check - onLoadRef will be updated with latest onLoad callback, and this will make sure that we always call most-recent version of the callback ( and thats something that I would expect from the callbacks ).

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