The vehicleCardHeader component is not visible on UI

Open Beginner friendly
#373 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
84/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
react, typescript
Domain
frontend

Research direction

Start in services/web/src/components/dashboard/dashboard.tsx and reproduce the dashboard vehicle-card rendering described in the issue. Check that the vehicle VIN and the “Vehicle Service History” and “Contact Mechanic” buttons are fully visible after the change.

Written by the indexing model from the issue text.

Description

bug

Bug

The vehicleCardHeader component is not visible on UI

On the dashboard, the vehicleCardHeader component (which displays the vehicle VIN, "Vehicle Service History" button, and "Contact Mechanic" button) is successfully is completely hidden from the user interface.

To Reproduce

  1. Log into the crAPI application.
  2. Add a new vehicle or navigate to the dashboard with an existing vehicle.
  3. Look at the vehicle card at the top. The vehicle image and details are visible, but the header containing the VIN and action buttons is missing.
  4. Inspect the DOM to see that the ant-page-header-heading is rendered but pushed out of view due to the .ant-card-meta-title constraints.
Image

Expected behavior

The vehicle's VIN and action buttons ("Vehicle Service History", "Contact Mechanic") should be fully visible at the top of the vehicle card.

Suggested fix

the <Meta> wrapper can be removed in services/web/src/components/dashboard/dashboard.tsx and the header/content placed directly inside the body:

diff
- <Meta
-   title={vehicleCardHeader(
-     vehicle,
-     handleVehicleServiceClick,
-     handleContactMechanic,
-   )}
-   description={vehicleCardContent(vehicle)}
- />
+ {vehicleCardHeader(
+   vehicle,
+   handleVehicleServiceClick,
+   handleContactMechanic,
+ )}
+ {vehicleCardContent(vehicle)

Runtime Environment

OS: Windows
Docker version: [e.g. Docker version 29.6.1
Browser: [Chrome 150.0.7871.101, Edge Version 150.0.4078.65]

Dominant language
Java
Stars
1.6k
Forks
645
Avg merge
37m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OWASP/crAPI

All issues in OWASP/crAPI

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.