Fix #168: Enatega Customer Application: Ratings or reviews percentage #1638
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KarliAitema
force-pushed
the
fix-issue-168
branch
4 times, most recently
from
aabef2b to
b052664
Compare
…s screen The percentage calculation for rating distribution was using restaurant.total (total count from backend) instead of the actual number of reviews in the displayed reviews array. This caused incorrect percentages when the reviews array contained a subset of all reviews. Changed to use reviews.length for the percentage calculation, which ensures the displayed percentages accurately reflect the distribution of the reviews that are actually being shown to the user. Co-Authored-By: Claude <noreply@anthropic.com>
KarliAitema
force-pushed
the
fix-issue-168
branch
from
b052664 to
2a29cc8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #168
Hey! 👋 I noticed issue #168 and wanted to help out.
What's Changed
This addresses the issue by making the necessary code changes.
Related Issue
Closes #168
Let me know if you'd like any changes! Happy to adjust.