Skip to content

Conversation

@alexcambose
Copy link
Contributor

Summary

Rationale

How has this been tested?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

@alexcambose alexcambose requested a review from a team as a code owner November 3, 2025 15:24
@vercel
Copy link

vercel bot commented Nov 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
component-library Ready Ready Preview Comment Nov 3, 2025 3:25pm
developer-hub Ready Ready Preview Comment Nov 3, 2025 3:25pm
entropy-explorer Ready Ready Preview Comment Nov 3, 2025 3:25pm
insights Ready Ready Preview Comment Nov 3, 2025 3:25pm
3 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
api-reference Skipped Skipped Nov 3, 2025 3:25pm
proposals Skipped Skipped Nov 3, 2025 3:25pm
staking Skipped Skipped Nov 3, 2025 3:25pm

Copy link
Contributor

@fhqvst fhqvst left a comment

Choose a reason for hiding this comment

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

lgtm

two tiny nits:

  • i'd probably not have the useEffects at all, but instead just keep all the logic in the copy callback
  • in theory i think we need to check if we're still mounted before we call setIsCopied, but in practice i don't think this matters

@alexcambose
Copy link
Contributor Author

yeah that's true, kinda just copy pasted that from the existing code. I can change it with the next pr.

@alexcambose alexcambose merged commit 20bb435 into main Nov 3, 2025
10 checks passed
@alexcambose alexcambose deleted the chore/copy-hook branch November 3, 2025 15:40
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