DEV Community

loading...
Cover image for Use the new Angular Clipboard CDK to interact with the clipboard
Angular

Use the new Angular Clipboard CDK to interact with the clipboard

Tim Deschryver
πŸ‘Ÿ Runner πŸ‘¨β€πŸ’» OSS enthusiast - NgRx, Angular Testing Library, MSW ✍ Blogger
Originally published at timdeschryver.dev ・Updated on ・3 min read

The helium-barbell (v9.0.0-next.1) release brings us a new CDK clipboard module to interact with the clipboard. In this post, we'll explore how to use the new CDK with some examples.

The Component Dev Kit (CDK) is a set of tools that implement common interaction patterns whilst being unopinionated about their presentation. It represents an abstraction of the core functionalities found in the Angular Material library, without any styling specific to Material Design. Think of the CDK as a blank state of well-tested functionality upon which you can develop your own bespoke components.

Import the ClipboardModule

The first step to use the CDK is to import the ClipboardModule from @angular/cdk/clipboard and add it to the imports declaration.

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { ClipboardModule } from '@angular/cdk/clipboard'

import { AppComponent } from './app.component';

@NgModule({
  imports: [
    BrowserModule,
    ClipboardModule
  ],
  declarations: [ AppComponent ],
  bootstrap:    [ AppComponent ]
})
export class AppModule { }
Enter fullscreen mode Exit fullscreen mode

Using the cdkCopyToClipboard attribute

After the ClipboardModule is imported, we're good to go.
The only thing needed to copy content is the cdkCopyToClipboard attribute.
It's possible to add it to any element, and when the element is clicked it will save the content to your clipboard.

<button cdkCopyToClipboard="πŸ‘‹ You copied me!">Click to copy</button>
Enter fullscreen mode Exit fullscreen mode

Copying a static string is boring, but we can also use a property binding to copy the result of an expression.

export class AppComponent {
  code = 'AAA-BBB-CCC'
}
Enter fullscreen mode Exit fullscreen mode
<input disabled [value]="code" />
<button [cdkCopyToClipboard]="code">Copy coupon code</button>
Enter fullscreen mode Exit fullscreen mode

Even more fun is to bind it to a function where we can modify the content.

export class AppComponent {
  value = ''

  copy(value) {
    return `${value}\n\ncopied from timdeschryver.dev`;
  }
}
Enter fullscreen mode Exit fullscreen mode
<textarea [(ngModel)]="value"></textarea>
<button [cdkCopyToClipboard]="copy(value)">Copy content</button>
Enter fullscreen mode Exit fullscreen mode

Using the Clipboard service

Using the cdkCopyToClipboard attribute is great to give users the possibility to copy content from a page.
But it doesn't allow us, as developers, to copy content programmatically. This is where the Clipboard service comes into play. By using the copy(content) method we can copy content to the clipboard.

<button (click)="generateId()">Generate Id</button>
Enter fullscreen mode Exit fullscreen mode
export class AppComponent {
  constructor(private clipboard: Clipboard) {}

  generateId() {
    const id = 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, c => {
      const r = Math.random() * 16 | 0, v = c == 'x' ? r : (r & 0x3 | 0x8);
      return v.toString(16);
   });

   this.clipboard.copy(id);

   alert(`Id "${id}" is generated and copied to the clipboard`);
  }
}
Enter fullscreen mode Exit fullscreen mode

Playground

Implementation details

Internally, the PendingCopy is used to copy content to the clipboard. This class creates an invisible textarea in the DOM with the content as its value. When the copy() method is used, it will move the focus to the invisible textarea and use the native execCommand('copy') to copy the content to the clipboard. As the last step, it will re-focus the previously selected element.

For the ones interested, the native Clipboard API can also cut content and read the current clipboard value.


Follow me on Twitter at @tim_deschryver | Originally published on timdeschryver.dev.

Discussion (0)