Usage
Badge surfaces concise status, counts, and categories beside titles, in table cells, or on map markers. Semantic colors communicate operational states operators must interpret quickly, so decorative accents should not hijack error or success hues. Dispatch uses badges widely in queue columns and incident rows; the rule that makes them work is vocabulary discipline—the same word means the same thing across modules.
text and BadgeIntent.Token. Corner radii follow shape in every state (Default uses size radii; Pill uses the full pill radius). Pass shape={BadgeShape.Pill} where ui-core used a full pill.Banner or body text.Button.Small in dense tables; Regular default; Large sparingly for focal indicators.Error, Warning, Success, and Info for meaningful operational states; Default and accent variants for neutral tagging.BadgeShape.Default uses size corner radii. BadgeShape.Pill on a static Beta, Insight, or solid Default badge uses a full radius. Queue-blue fills still depend on a Chroma token; use BadgeIntent.Informative solid until queue-blue-solid ships.BadgeType.Beta is the accent preview chip (Tinted or Solid); it does not take intent or color. BadgeType.Insight is an outlined chip with no fill; it does not take intent, color, or appearance.icon is set with no children, the badge is square. Pair with aria-label so meaning is not color- or glyph-only; the component shows that value in a tooltip on hover.formatMessage; parallel phrasing within a column.aria-label that names the state ("Live", "Shared"). That label doubles as the tooltip content.Success for informational labels that aren't positive outcomes.