Skip to content

Fix RepoCard star display and translations #205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

alichherawalla
Copy link
Contributor

@alichherawalla alichherawalla commented May 20, 2025

Summary

  • handle zero-star repositories correctly
  • fix translation typos
  • update styles for HomeContainer cards
  • add tests for zero-star case

Testing

  • yarn test (fails: package not in lockfile)

Summary by CodeRabbit

  • Bug Fixes
    • Star counts of zero are now correctly displayed for repositories, instead of showing an unavailable message.
    • Fixed typos in English translation strings and test IDs, correcting "unavaiable" to "unavailable".
  • Style
    • Improved card component styling by ensuring max-width is set in pixels and color is applied only when specified.
  • Tests
    • Added a test to verify that a star count of zero is rendered correctly.

Copy link
Contributor

coderabbitai bot commented May 20, 2025

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (2)
  • app/components/ProtectedRoute/tests/__snapshots__/index.test.js.snap is excluded by !**/*.snap
  • app/containers/HomeContainer/tests/__snapshots__/index.test.js.snap is excluded by !**/*.snap

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

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

Walkthrough

The updates address rendering logic, styling, and translation corrections. RepoCard now displays a star count of zero, with a corresponding test added. Styling for CustomCard ensures pixel units and conditional color application. Multiple spelling errors in English translation keys and messages are corrected from "unavaiable" to "unavailable".

Changes

File(s) Change Summary
app/components/RepoCard/index.js Adjusted logic to display star count even when zero; fallback message logic unchanged.
app/components/RepoCard/tests/index.test.js Added test for zero star count display; fixed typo in test ID for unavailable stars.
app/containers/HomeContainer/index.js Ensured "px" units for max-width style; color style now conditionally applied if provided.
app/translations/en.js, app/translations/en.json Fixed "unavaiable" typo to "unavailable" in translation keys and messages.

Poem

In the garden of code, where stars sometimes are none,
Even zero now shines, the fix is well-done!
With “unavailable” spelled right,
And pixels set just right,
The translations and styles hop into the sun.
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
app/components/RepoCard/index.js (1)

46-46: Good fix for handling zero stars!

This change correctly handles repositories with zero stars by explicitly checking for stargazersCount === 0 in the condition. Without this check, JavaScript would evaluate 0 as falsy and incorrectly show the unavailable message.

Format the condition according to prettier's rules:

-      <If condition={stargazersCount || stargazersCount === 0} otherwise={<T data-testid="stargazers-unavailable" id="repo_stars_unavailable" />}>
+      <If 
+        condition={stargazersCount || stargazersCount === 0}
+        otherwise={<T data-testid="stargazers-unavailable" id="repo_stars_unavailable" />}
+      >
🧰 Tools
🪛 ESLint

[error] 46-46: Replace ·condition={stargazersCount·||·stargazersCount·===·0}·otherwise={<T·data-testid="stargazers-unavailable"·id="repo_stars_unavailable"·/>} with ⏎········condition={stargazersCount·||·stargazersCount·===·0}⏎········otherwise={<T·data-testid="stargazers-unavailable"·id="repo_stars_unavailable"·/>}⏎······

(prettier/prettier)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 7740866 and 0dbdcc5.

⛔ Files ignored due to path filters (1)
  • app/components/RepoCard/tests/__snapshots__/index.test.js.snap is excluded by !**/*.snap
📒 Files selected for processing (5)
  • app/components/RepoCard/index.js (1 hunks)
  • app/components/RepoCard/tests/index.test.js (1 hunks)
  • app/containers/HomeContainer/index.js (1 hunks)
  • app/translations/en.js (1 hunks)
  • app/translations/en.json (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
app/components/RepoCard/index.js (1)
app/components/T/index.js (1)
  • T (22-28)
🪛 ESLint
app/components/RepoCard/index.js

[error] 46-46: Replace ·condition={stargazersCount·||·stargazersCount·===·0}·otherwise={<T·data-testid="stargazers-unavailable"·id="repo_stars_unavailable"·/>} with ⏎········condition={stargazersCount·||·stargazersCount·===·0}⏎········otherwise={<T·data-testid="stargazers-unavailable"·id="repo_stars_unavailable"·/>}⏎······

(prettier/prettier)

🔇 Additional comments (5)
app/translations/en.json (1)

5-5: Spelling corrections look good!

Fixed the typo in the translation keys from "unavaiable" to "unavailable" which improves the quality of user-facing text.

Also applies to: 10-10

app/translations/en.js (1)

1-1: Spelling corrections consistently applied!

Fixed the typo from "unavaiable" to "unavailable" in the translation strings, maintaining consistency with the JSON translation file.

app/components/RepoCard/tests/index.test.js (2)

35-43: Good test coverage for zero stars case!

This test appropriately verifies that repositories with zero stars display the star count instead of the unavailable message, matching the fix in the component.


52-52: Fixed test ID spelling consistency

Corrected the test ID from 'stargazers-unavaiable' to 'stargazers-unavailable', matching the spelling fixes in the translation files.

app/containers/HomeContainer/index.js (1)

28-29: Good fix for explicit CSS unit specification.

Adding the "px" unit to the maxwidth property is a critical fix for proper CSS rendering. Without explicit units, browsers may interpret numeric values inconsistently or ignore them entirely, leading to styling issues.

The change also improves code consistency since the Container component (line 41) already follows this pattern by using the "px" unit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant