Adds a copy button and truncation to title

[Mbeaulne]

Description

This may be a little much, but I think its pretty cool (and self contained!)

Added a new CopyText component that allows users to copy text to clipboard with visual feedback. Implemented this component in the AppMenu to make the title copyable.

Related Issue and Pull requests

Type of Change

• Bug fix
• New feature
• Improvement
• Cleanup/Refactor
• Breaking change
• Documentation update

Checklist

• I have tested this does not break current pipelines / runs functionality
• I have tested the changes on staging

Screenshots (if applicable)

title.mov (uploaded via Graphite)

before:

after:

Test Instructions

1. Navigate to any page with a title in the app menu
2. Hover over the title to see the copy button appear
3. Click either the title or the copy button to copy the text
4. Verify the visual feedback (green check mark and brief flash effect)

Additional Comments

The CopyText component provides the following features:

• Click to copy functionality
• Visual feedback with a brief flash effect when copied
• Icon transition between copy and check mark
• Configurable display of the copy button

[Mbeaulne]

• Fixes knip #1482
• Abstracts artifacts list #1481
• cleans up pipelineDetails v2 #1480
• cleans up pipelineDetails v1 #1479
• Removes icons next to title in run and editor #1478
• Adds copy to other titles #1477
• Adds a copy button and truncation to title #1476 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[camielvs]

obviously we only want to copy strings and not jsx elements, but something about children: string instead of children: ReactNode feels weird to me. I won't block on this, but I did want to flag it because it seems somewhat like an antipattern

[Mbeaulne]

I think its fine because the result of anything but a string will throw a type error

[camielvs]

I did see this also, which is why I'm not blocking. That doesn't make it feel any less weird though 😅

[camielvs]

this is a red flag to me. A null variant button? Hmmmm. That suggests to me there's a major gap in our coverage of button styles. I think I'd rather see a new variant added than a custom button made in-place via null

[camielvs]

Not sure about the null button variant but otherwise LGTM

[Mbeaulne]

Merge activity

• Dec 5, 10:00 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Dec 5, 10:01 PM UTC: Graphite rebased this pull request as part of a merge.
• Dec 5, 10:02 PM UTC: @Mbeaulne merged this pull request with Graphite.