feat: add button to copy the item URL

[zebrapurring]

What type of PR is this?

• feature

What this PR does / why we need it:

It can be useful to be able to copy an item's URL (especially from the PWA on mobile devices, where the URL bar is not visible).

Which issue(s) this PR fixes:

No issues.

Special notes for your reviewer:

-

Testing

Enter the item page for an asset and click the copy button next to the QR code generation.

Summary by CodeRabbit

• New Features

  • Introduced a button to copy the current URL, enhancing user interaction.
  • Added a QR code component alongside the copy URL button for easy sharing.

• Style

  • Styled the new button as a circular ghost button to indicate its secondary action nature.

[coderabbitai]

Walkthrough

The pull request modifies the frontend/pages/item/[id]/index.vue file by introducing two new computed properties: currentUrl and currentPath. These properties capture the current window URL and route path, respectively. A new button is added to the template, enabling users to copy the current URL, which is displayed alongside a QR code component. The changes enhance user interaction by providing a convenient way to share the current page's URL.

Changes

File	Change Summary
frontend/pages/item/[id]/index.vue	- Added currentUrl computed property to get current window URL - Added currentPath computed property to get current route path - Introduced a new button for copying the current URL

Suggested reviewers

• tankerkiller125

Security Recommendations

1. URL Copying Mechanism:

   • Ensure the URL copying functionality uses a secure method like navigator.clipboard.writeText()
   • Validate and sanitize the URL before copying to prevent potential XSS risks
   • Implement proper error handling for clipboard operations

2. Client-Side URL Generation:

   • Use server-side or framework-provided URL generation methods instead of directly accessing window.location
   • Implement URL validation to prevent potential security vulnerabilities

3. QR Code Generation:

   • Verify that the QR code generation process does not expose sensitive information
   • Ensure the QR code links are validated and sanitized

Possibly related PRs

• feat: duplicate item button #259: Modifications to Vue components in the frontend/pages/item/[id]/ directory, adding similar user interaction button functionality

---

📜 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 5d593c6 and fcba843.

📒 Files selected for processing (1)

• frontend/pages/item/[id]/index.vue (2 hunks)

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

• frontend/pages/item/[id]/index.vue

---

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

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

[coderabbitai]

Caution

Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.

Actionable comments posted: 1

🛑 Comments failed to post (1)

frontend/pages/item/[id]/index.vue (1)

389-391: ⚠️ Potential issue

Consider implementing URL sanitization for security

The direct use of window.location.href could potentially expose sensitive information in URL parameters. Consider implementing URL sanitization before copying.

Here's a suggested implementation:

 const currentUrl = computed(() => {
-  return window.location.href;
+  const url = new URL(window.location.href);
+  // Remove sensitive parameters if any
+  url.searchParams.delete('token');
+  url.searchParams.delete('session');
+  return url.toString();
 });

Committable suggestion skipped: line range outside the PR's diff.