IncidentsWidget
When to use
Section titled “When to use”Store ops home dashboards showing active incidents. Requires BFF incidents API and auth token.
When NOT to use
Section titled “When NOT to use”Without NikeStoreProvider or explicit storeNumber. Non-ServiceNow ticketing.
Podium primitives composed
Section titled “Podium primitives composed”- Podium
Text - Podium
Link - Podium
Skeleton
Required providers
Section titled “Required providers”- NikeStoreProvider
- ModuleAnalyticsProvider
Auto-generated from
src/components/StoreIncidents/StoreIncidents.tsx. Do not edit by hand. Runpnpm docs:propsafter changing source JSDoc.
IncidentsWidgetProps
Section titled “IncidentsWidgetProps”| Prop | Type | Required | Description |
|---|---|---|---|
accessToken |
null | string |
Yes | SIM user JWT (Okta or Retail) used as Authorization: Bearer <token> on every BFF call. When null, the incident fetch will fail with a 401 — the host should keep this in sync with its auth store. |
baseUrl |
string |
Yes | BFF incidents base URL (e.g. ‘/sim-bff/incidents’) |
limit |
number |
No | Max incidents to display |
services |
IncidentsWidgetServices |
No | Injectable service overrides for Storybook/tests |
storeNumber |
string |
No | Override store number (defaults to NikeStoreProvider context) |
Examples
Section titled “Examples”Store incidents panel
Section titled “Store incidents panel”import { IncidentsWidget } from '@nike/whisker-component-library';
<IncidentsWidget accessToken={token} baseUrl="/sim-bff/incidents" limit={10} />;