Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Interactive Rating Component using React JS

bem, itcss, react
Madan Sinha•300
@lazy4gyan
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone!

This is my first React based challenge. I have tried my best to complete this challenge as per my knowledge, if you think this could be done better then please do not hesitate to reply, I will take care of all the suggestions and try to implement in my future projects.

Happy Coding😊

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello Madan Shina congrats on finishing the challenge!

    Your component seems to work perfectly and adjust correctly to the UI, let me give you some advices for React that maybe can help you in the future. Some of this advices are bit of an overkill for a little application like this one, but practicing them can help you a lot when building bigger React Apps.

    1. Instead of having all your code on Rating.js, try building each component apart and then rendering in your main component, this will make your code more readable and structured, instead of having a big chunk file with all the JSX inside!

    2. Don't use globals style to style every component like in a normal html, css, javascript project, try using either CSS modules or Styled Components, you can learn more of them clicking on the links, my preferred option is styled components since they are easy to pass props, change styles, reuse them, but CSS modules are also a great approach (you can use them with SCSS too)

    3. You don't need to import React from 'react', this was added like 1 or 2 years ago, there is no longer the need to do it!, you can just import parts of react like import {useState} from 'react' and so on!

    Hope my feedback helps you in future challenges, don't hesitate to ask any question, good job!

    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