fix: Copy button on blog post page not working

[vishallvkg]

What does this PR do?

The copy button on the blog post was not working (earlier)

Earlier

Now

Test Plan

There were no Test Plans

Related PRs and Issues

#2605

Have you read the [Contributing Guidelines on issues]

Yes

Summary by CodeRabbit

Release Notes

• New Features
  • Added visual feedback tooltip displaying "Copied!" confirmation when users copy shared content to clipboard.
  • Enhanced share button interactions with improved tooltip component for clearer user feedback during sharing actions.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A single component file was modified to enhance copy-to-clipboard functionality. The change removes a dependency on the page state object and integrates a Tooltip component with melt UI library. The copy action now utilizes a state handler that tracks whether content has been copied, displaying dynamic tooltip text that reflects the current state—"Copied!" when the action completes, otherwise "Copy". The existing link-sharing behavior is preserved while non-link share actions receive improved interaction feedback.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Review of new Tooltip and melt UI integration pattern
• Verification of handleCopy utility and state management logic
• Confirmation that link-sharing behavior remains intact after refactoring
• Assessment of tooltip content binding and state synchronization

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: fixing a non-working copy button on the blog post page, which aligns with the changeset that adds Tooltip integration and improved copy functionality to the share action.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/lib/components/blog/post-meta.svelte (1)

16-26: Consider guarding copy behavior when currentURL is empty

If currentURL can ever be omitted or empty, handleCopy(currentURL, 2000) will cause the copy button to silently copy an empty string. You might want to either (a) make currentURL a required prop for this component, or (b) conditionally render/enable the copy UI only when currentURL is non-empty.

Also applies to: 32-33

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c9e5b9 and 444d05b.

📒 Files selected for processing (1)

• src/lib/components/blog/post-meta.svelte (3 hunks)

🔇 Additional comments (2)

src/lib/components/blog/post-meta.svelte (2)

7-8: Tooltip + Melt imports look correct for current usage

Importing Tooltip from your local components and melt from @melt-ui/svelte aligns with how the button is wired later with use:melt={trigger}; no changes needed here.

---

81-82: Copy button + tooltip wiring correctly addresses the original issue

Wiring the non-link share option to onclick={copy} and driving the tooltip text from $copied ? 'Copied!' : 'Copy' gives clear feedback and should resolve the previously non-working copy button, assuming currentURL is populated. This also matches Svelte 5 runes-style event handling (onclick) and store usage.

Also applies to: 95-107