Show full inspector information on report skin inspector display

Objective

  • Make inspector information on the client report ("report skin") readable in full, especially license / certificate text that is currently cut off with an ellipsis.
  • Align the header inspector block with the expectation that nothing important is hidden behind single-line truncation when space allows or via an acceptable overflow pattern.

Background

  • Product feedback (roadmap item) called out that the certificate number (or equivalent credential line) does not fully show in the UI.
  • The client report experience lives under src/app/client/reports/ and is composed from shared components; truncation is a presentation choice, not a data limitation, until proven otherwise.

Scope

Frontend (attik-frontend)

  • The top Inspector card on the published client report is rendered in src/app/client/reports/components/ReportHeader.tsx. Each inspector row uses a min-w-0 text column with Tailwind truncate on both the name and the credentials line (inspector.credentials), which forces single-line overflow with ellipsis—this is the most direct match for "certificate number" / credential text being unreadable when long.
  • That header is mounted from the report page at src/app/client/reports/[slug]/page.tsx, which passes the hydrated Report into ReportHeader.
  • Inspector shape for this surface is defined in src/app/client/reports/types.ts (Inspector.credentials, plus other optional fields such as contact_info, tx_wdi_license, trec_sponsor). If the fix is "show everything," consider whether only credentials should wrap, or whether name and other inspector fields that are not currently shown in the header belong in scope.
  • Elsewhere on the same report, src/app/client/reports/components/InspectorSignatureSection.tsx already prints name and credentials in flowing text (no truncate on that combined line), so behavior may differ between header vs signature block—worth reconciling for consistency only if product wants both surfaces identical.

Backend

  • No backend route or schema was identified in this pass that explicitly names credentials under a report-prefixed module; scope is likely frontend display unless investigation shows missing or shortened data from the API.

Decision needed

  • Whether wrapping (multi-line), tooltip / expand, or layout change (e.g. wider column, stack below avatar) is preferred on narrow / mobile widths, and whether inspector name must also stop truncating when "all information" is required.

References

Please authenticate to join the conversation.

Upvoters
Status

Planned

Board
🏠

Main App

Date

2 months ago

Author

Linear

Subscribe to post

Get notified by email when there are changes.