{
  "id": 5381412,
  "title": "Adding Dynamic Dropdowns for “Modelo” & “Lineup” in Device Detail & Fixing the “TVs sin uso” Card",
  "url": "https://urgent.news/2026/09/03/adding-dynamic-dropdowns-for-modelo-lineup-in-device-detail-fixing",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-03T18:13:05.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/zaerohell/adding-dynamic-dropdowns-for-modelo-lineup-in-device-detail-fixing-the-tvs-sin-uso-card-2mpg"
  },
  "original_language": "en",
  "account": "The Device Detail screen originally displayed free-text inputs for Model and Lineup, allowing users to enter any combination of characters. This practice resulted in inconsistent data being collected, with entries such as \"Model-X\", \"modelx\", and \"Model X\" polluting analytics. To resolve this, I centralized the known values for Model and Lineup in a dedicated constants file, allowing the UI to enforce consistency.",
  "summary": "Adding Dynamic Dropdowns for “Modelo” & “Lineup” in Device Detail & Fixing the “TVs sin uso” Card TL;DR: I refactored DeviceDetailSheet.tsx to replace static selects with memoized dropdowns limited to known values, and patched dashboard.service.ts to filter out public‑space rooms from the “TVs sin uso” metric. Both changes tighten the UI and improve data accuracy. The Problem The Device Detail…",
  "key_points": [
    "Centralized Model and Lineup values in constants file",
    "Enforced consistency, eliminated inconsistent data",
    "Improved analytics quality"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}