feat: add rating display

[gerardogreco-blx]

No description provided.

[gerardogreco-blx]

@claude

[claude]

Claude finished @gerardogreco-blx's task in 1m 26s —— View job

---

Code Review: feat: add rating display

• Gather context and read changed files
• Analyze PR diff
• Provide code review feedback

---

The PR adds a rating display (star icons + numeric value + review count) to the clothing item cards on the index page. The implementation is generally solid, but there are a few issues worth addressing.

---

Issues Found

1. Potential N+1 / Inefficient Data Loading — Reviews.Count (Medium)

File: src/ClaudeClothes.Web/Pages/Index.razor, line 98

<span class="review-count">(@clothingItem.Reviews.Count)</span>

This accesses the Reviews navigation property to get a count. On the index page, this means the service query must eagerly load all reviews for every item just to display a count — which is expensive and grows with the dataset.

Since AverageRating is already a precomputed/stored field on ClothingItem, a ReviewCount property should be added to the model as well and kept in sync. This avoids loading the entire reviews collection on the listing page.

Alternatively, if Reviews is already included in the query (via .Include()), consider whether that's appropriate at this layer.

Fix this →

---

2. Localization Inconsistency (Minor)

The rest of the UI is in Italian, but the new additions use English strings:

• Line 111: "View Details" (was previously "Vedi Dettagli")
• Line 110: aria-label="View details of @clothingItem.Name" (was "Vedi i dettagli di @clothingItem.Name")
• Line 103: "No reviews" (should be something like "Nessuna recensione")

Fix this →

---

3. Half-Star Logic Edge Case (Minor)

File: src/ClaudeClothes.Web/Pages/Index.razor, lines 83–94

if (i <= Math.Floor(clothingItem.AverageRating))
{
    // full star
}
else if (i - clothingItem.AverageRating < 1)
{
    // half star
}

The condition i - clothingItem.AverageRating < 1 correctly identifies the transitional star position, but it will show a half-star even for ratings like 3.9 (where many users would expect a nearly-full star). There's no threshold check — any fractional part, however small, triggers the half-star icon. Consider applying a minimum threshold (e.g., only show half-star if the fractional part >= 0.25):

else if (i - clothingItem.AverageRating < 1 && (i - 1) < clothingItem.AverageRating)
{
    // half star
}

Actually the existing condition is functionally equivalent to this, so this is more about intentionality. The only real edge is whether a 3.05 rating should show a half star at position 4 — which the current code does. This is acceptable but worth documenting as intentional.

---

Positive Notes

• Good use of role="img" and aria-label on the star container for screen reader accessibility.
• The @if (clothingItem.AverageRating > 0) guard correctly handles items with no ratings.
• CSS is well-organized and consistent with the existing design system.
• The dashed separator (border-top: 3px dashed #1A1A1A) cleanly separates the footer section from the card body.

---

Summary

Issue	Severity
Reviews.Count requires loading full collection	Medium
English strings in Italian UI	Minor
Half-star threshold not explicitly bounded	Minor

The most important issue to address before merging is the Reviews.Count data loading concern — it may work fine today with small datasets but will degrade as data grows.