CircleBadge

Use circle badge to visually connect logos of third-party services like in the marketplace.
  • Alpha
  • Not reviewed for accessibility
This documentation is moving to a new home. Please update any link or bookmark that points to this page. The new content can be found here.
import {CircleBadge} from '@primer/react'

Use CircleBadge to visually connect logos of third party services like in marketplace. Use CircleBadge.Icon to add an Octicon to the CircleBadge.

Examples

Props

CircleBadge

NameTypeDefaultDescription
variant
'small' | 'medium' | 'large'
'medium'

Creates a smaller or larger badge. Has no effect if the size prop is set

size
number

Sets the size of the badge in pixels. Overrides the variant prop when set

inline
boolean
false

Styles the badge to display: inline

ref
React.RefObject<HTMLDivElement>
as
React.ElementType
"div"

The underlying element to render — either a HTML element name or a React component.

sx
SystemStyleObject

CircleBadge.Icon

NameTypeDefaultDescription
as
React.ElementType
Octicon

The underlying element to render — either a HTML element name or a React component.

Additional props are passed to the <Octicon> element. See Octicon docs for a list of props accepted by the <Octicon> element.

Status

Alpha

  • Component props and basic example usage of the component 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 robust unit test coverage (100% where achievable).
  • Component has visual regression coverage of its default and interactive states.
  • Component does not introduce any axe violations.
  • Component has been manually reviewed by the accessibility team and any resulting issues have been addressed.

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 does not introduce any performance regressions.

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.
  • Tooling (such as linters, codemods, etc.) exists to prevent further use of alternatives.