Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Interactive Rating Component (React and Tailwind)

react, tailwind-css
mehdias63•330
@mehdias63
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ehsan Tatasadi•1,800
    @tatasadi
    Posted over 1 year ago

    Hey Mehdi,

    Great job on implementing the rating card component! This is a solid example of utilizing React's state management and conditional rendering to create a responsive UI. Let's address the feedback to refine your code further.

    Corrections and Improvements:

    • The extra comma in the Rate component's className (isSelected ? "bg-light-gray , text-white" : "") should be removed.

    • In addition, to apply default styles when isSelected is false, you should move the default classes to the other side of the ternary operator to ensure they are applied correctly and avoid having two background and text colors.

    Corrected Code:

    className={`${isSelected ? "bg-light-gray text-white" : "bg-dark-blue text-light-gray"} w-9 h-9 lg:w-[3.1875rem] lg:h-[3.1875rem] rounded-full flex justify-center items-center hover:bg-orange hover:text-white cursor-pointer`}
    
    • There's a missing space in the lg:text-[0.9375rem]font-normal class, and since font-normal is the default font weight, you can omit it unless you're overriding a different font weight set elsewhere.

    By implementing these suggestions, your code becomes cleaner and more efficient, enhancing readability and maintainability. Keep up the great work, and continue refining your skills with each project you tackle!

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub