Skip to content

[US-4.4 / OBT-207] Render one badge per platform - #17

Open
levigtri wants to merge 4 commits into
levigft/obt-206-us-43-select-multiple-platforms-independently-web-androidfrom
levigft/obt-207-us-44-see-individual-platform-badges-for-each-app-eg-web
Open

[US-4.4 / OBT-207] Render one badge per platform#17
levigtri wants to merge 4 commits into
levigft/obt-206-us-43-select-multiple-platforms-independently-web-androidfrom
levigft/obt-207-us-44-see-individual-platform-badges-for-each-app-eg-web

Conversation

@levigtri

@levigtri levigtri commented Jul 5, 2026

Copy link
Copy Markdown
Member

Summary

US-4.4 / OBT-207 — Show one platform badge per platform for each app so users can tell at a glance which platforms an app targets, replacing the single combined label.

Changes

  1. New src/constants/platforms.ts — single source of truth for platform options and display labels (platformLabel). PlatformMultiSelect now consumes PLATFORM_OPTIONS from here.
  2. dashboard/AppCard.tsx: render one <Badge> per entry in app.platforms; removed the old platformLabel() switch that converted a single combined value.
  3. AppsPage.tsx: the app grid renders one badge per platform (wraps on multiple).
  4. AppDetailPage.tsx: the detail header renders one badge per platform.

Badges render correctly for apps with 1, 2, or 3 platforms.

Type of Change

  • Feature

Testing

  • npm run typecheck — pass
  • npm run lint — 0 errors (pre-existing ProjectsPage warning only)
  • npm run build — pass

Stacked: US-4.2 (#15) → US-4.3 (#16) → US-4.4 (this). Merge in that order.
Depends on backend US-4.1 / OBT-204 (PR #94) for runtime validation.

Show an individual badge for each entry in the app's platforms array on the
dashboard app cards, the Manage Apps grid, and the app detail page, instead of a
single combined label. Centralize the platform display labels in
constants/platforms and drop the old platformLabel switch in AppCard.
levigtri and others added 3 commits July 9, 2026 22:08
These pr-us-*.md files are local PR notes that were bundled into the
feature commit by mistake; they should never have been tracked/pushed.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Local decision notes bundled into the feature commit by mistake; never
meant to be tracked/pushed.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Pro Plus

Run ID: 03df0e02-8048-4f04-b38e-f9acca2d1666

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch levigft/obt-207-us-44-see-individual-platform-badges-for-each-app-eg-web

Comment @coderabbitai help to get the list of available commands.

@levigtri levigtri self-assigned this Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant