Skip to content

Token

Alpha
A Token represents a piece of data. They are typically used to show a collection of related attributes.

The default Token can be used for most cases, but specialized token components are provided for specific use cases (see below for more info).

All types of tokens may have the same interactive qualities as links or buttons. They also have a sense of being "selected" and ready for user interaction such as being removed from a collection.

Examples

Basic

Kitchen sink

With leadingVisual

A leadingVisual should not be used with the small size option if you're rendering an icon from Octicons

Interactive tokens

If any token is interactive (it is a link or a button), it will become focusable, and react to being hovered or focused on.

If a token is interactive and has a remove button (appears when passing onRemove), the remove button should not get focus. To invoke the onRemove callback without using the cursor, press 'Backspace' when the token is focused.

These rules apply to all token components mentioned in this document.

Interactive tokens with and without an onRemove prop

IssueLabelToken

Tokens that represent Issue labels should use the IssueLabelToken component.

AvatarToken

Tokens that represent GitHub users should use the AvatarToken component.

This component should not be used with the small or medium size option

Props

Token

No props

IssueLabelToken

No props

AvatarToken

No props

Status

Alpha

  • Component props are documented on primer.style/react.
  • Component does not have any unnecessary third-party dependencies.
  • Component can adapt to different themes.
  • Component can adapt to different screen sizes.
  • Component has 100% test coverage.

Beta

  • Component is used in a production application.
  • Common usage examples are documented on primer.style/react.
  • Common usage examples are documented in storybook stories.
  • Component has been reviewed by a systems designer and any resulting issues have been addressed.
  • Component has been manually reviewed by the accessibility team and any resulting issues have been addressed.

Stable

  • Component API has been stable with no breaking changes for at least one month.
  • Feedback on API usability has been sought from developers using the component and any resulting issues have been addressed.
  • Component has corresponding design guidelines documented in the interface guidelines.
  • Component has corresponding Figma component in the Primer Web library.
Edit this page on GitHub
2 contributorsmperrotticolebemis
Last edited by mperrotti on March 29, 2022