@mediaradar/design-components 0.6.0 → 0.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -5,9 +5,8 @@ components genuinely common across consuming apps (`insights-studio-prototype`,
5
5
  `mr-clientapps-insights-studio`), published as a real npm package so there's
6
6
  structurally only one implementation instead of two that can silently drift.
7
7
 
8
- **Status: spike/pilot.** One component (`InfoTip`) so far, not yet published
9
- to the real npm registry, not yet consumed by `mr-clientapps-insights-studio`
10
- at all. See `gh-design-system`'s open spike PR for the current state.
8
+ Published to npm and consumed by `insights-studio-prototype`. See
9
+ `CHANGELOG.md` for what each version contains.
11
10
 
12
11
  ---
13
12
 
@@ -24,6 +23,16 @@ components, for example), forcing it into a shared package is a downgrade
24
23
  for whichever app had the better version, not an improvement. Leave it
25
24
  where it is.
26
25
 
26
+ **Exception: generic design-system primitives** (decided 2026-09-25).
27
+ Basic building blocks like `Button`, `Toggle`, `AISpark` and `Freshness`
28
+ belong here even without an `mr-clientapps` duplicate. Two reasons: shared
29
+ components are built on them (`FilterDropdownFooter` and `NameListModal`
30
+ can't move without `Button`), and the component catalog and style guide
31
+ are moving to read from this package alone, so a primitive left behind
32
+ would drop out of both. Page- or data-specific components with no
33
+ duplicate (`EmbeddedFrame`, `ParkedSection`) still stay in their app, and
34
+ out of the catalog.
35
+
27
36
  **The escape hatch — a genuine conflict discovered mid-migration.** Sometimes
28
37
  a component looks like a good candidate until reconciliation actually starts,
29
38
  and it turns out the two apps need behavior that's genuinely incompatible —