@bytebrand/fe-ui-core-autobahn 1.0.119 → 1.0.120

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bytebrand/fe-ui-core-autobahn",
-  "version": "1.0.119",
+  "version": "1.0.120",
   "description": "auto.de md3 (Autobahn) design system — UI primitives, cards, chrome, VDP modules, theme CSS and locales. Ships raw TypeScript source (like fe-ui-core before it); each consumer's bundler compiles it.",
   "main": "index.ts",
   "license": "UNLICENSED",

package/vdp/index.ts

@@ -71,7 +71,7 @@ export type {
 } from './VdpModules';
 
 // View-model types + the spec-table helper.
-export { defaultVdpSpecs } from './types';
+export { defaultVdpSpecs, isZeroSpecValue } from './types';
 export type {
   VehicleDetail,
   VehicleCondition,

package/vdp/types.ts

@@ -20,6 +20,39 @@ export type { AutobahnPhev };
 /** One row of the Fahrzeugdaten spec table: [kebab-case lucide icon, label, value]. */
 export type VdpSpec = readonly [icon: string, label: string, value: string];
 
+// ---------------------------------------------------------------------------
+// Zero-value spec visibility (CDP ticket "Hide meaningless zero-value vehicle
+// attributes") — the single shared rule behind whether a Fahrzeugdaten row
+// renders when its underlying measurement is 0.
+//
+// Most numeric vehicle attributes (Leergewicht, Hubraum, Drehmoment, …) are
+// physical measurements that are never legitimately 0 — a 0 there means "no
+// data", not "the car weighs nothing", and rendering "0 kg" actively damages
+// trust in the data (the reported bug). The DEFAULT for a numeric spec is
+// therefore to hide the row entirely rather than show a fabricated-looking
+// zero.
+//
+// That default must NOT apply blindly to every field, per two carve-outs:
+//   - some fields have a real, meaningful zero (0 Vorbesitzer = never owned,
+//     0 km = brand-new car) — callers opt these OUT of hiding explicitly;
+//   - the Pkw-EnVKV legally-required consumption/emissions figures (cons,
+//     co2, co2class, and by the same regulatory family Verbrauch innerorts/
+//     außerorts) must never be suppressed by this generic rule — their own
+//     compliance/data-quality logic decides what renders, so callers building
+//     those rows must never run them through this check at all.
+//
+// isZeroSpecValue operates on the already-FORMATTED display string (not the
+// raw number) because callers combine both string-typed values (decorated
+// getters that already bake in a unit, e.g. "0 kg") and plain numbers
+// (`${n} Sitze`) into the same VdpSpec value slot — checking the rendered
+// string is the one place both shapes agree. It matches a leading zero
+// magnitude (optionally with an all-zero decimal, "0,0"/"0.0") followed by
+// whitespace (a unit) or end-of-string, so "0 kg"/"0,0 l/100 km"/"0" all
+// count as zero but "10 kg"/"0.5 l" (a real non-zero measurement) do not.
+export function isZeroSpecValue(formatted: string): boolean {
+  return /^-?0([.,]0+)?(\s|$)/.test(formatted.trim());
+}
+
 /**
  * Grouped equipment: each entry is a section title mapped to its item labels,
  * e.g. { Komfort: ['Klimaautomatik', …], Sicherheit: [...] }. Replaces the design
@@ -200,20 +233,27 @@ export interface VehicleDetail {
  * Build the design's twelve-row Fahrzeugdaten table from the typed fields. Used
  * when a VehicleDetail carries no explicit `specs`. Pure — produces the same rows
  * and order as the spec's ScreenVDP `specs` array.
+ *
+ * `allowZero: true` marks fields where 0 is a real, meaningful value (or isn't a
+ * zero-able numeric at all) — everything else gets the isZeroSpecValue default
+ * (hide the row rather than render a fabricated-looking "0 X"). cons/co2class
+ * are Pkw-EnVKV legally-required and are marked allowZero for that reason, not
+ * because 0 is plausible there — see isZeroSpecValue's own comment.
  */
 export function defaultVdpSpecs(v: VehicleDetail): VdpSpec[] {
-  return [
-    ['gauge', 'Kilometerstand', `${v.km.toLocaleString('de-DE')} km`],
-    ['calendar', 'Erstzulassung', v.reg],
-    ['zap', 'Leistung', v.power],
-    ['fuel', 'Kraftstoff', v.fuel],
-    ['cog', 'Getriebe', v.gear],
-    ['users', 'Sitze', `${v.seats} Sitze`],
-    ['door-open', 'Türen', `${v.doors} Türen`],
-    ['user', 'Halter', `${v.owners}. Hand`],
-    ['palette', 'Außenfarbe', v.color],
-    ['car-front', 'Karosserie', v.body],
-    ['droplet', 'Verbrauch komb.', v.cons],
-    ['leaf', 'CO₂ · Klasse', `${v.co2} · ${v.co2class}`],
+  const rows: ReadonlyArray<readonly [spec: VdpSpec, allowZero: boolean]> = [
+    [['gauge', 'Kilometerstand', `${v.km.toLocaleString('de-DE')} km`], true], // Neuwagen: 0 km is valid
+    [['calendar', 'Erstzulassung', v.reg], true],
+    [['zap', 'Leistung', v.power], true],
+    [['fuel', 'Kraftstoff', v.fuel], true],
+    [['cog', 'Getriebe', v.gear], true],
+    [['users', 'Sitze', `${v.seats} Sitze`], false],
+    [['door-open', 'Türen', `${v.doors} Türen`], false],
+    [['user', 'Halter', `${v.owners}. Hand`], true], // 0 Vorbesitzer is valid
+    [['palette', 'Außenfarbe', v.color], true],
+    [['car-front', 'Karosserie', v.body], true],
+    [['droplet', 'Verbrauch komb.', v.cons], true], // Pkw-EnVKV — exempt from this rule
+    [['leaf', 'CO₂ · Klasse', `${v.co2} · ${v.co2class}`], true], // Pkw-EnVKV — exempt
   ];
+  return rows.filter(([spec, allowZero]) => allowZero || !isZeroSpecValue(spec[2])).map(([spec]) => spec);
 }