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

Simple rating component

react, sass/scss
Nika•180
@nikavolk
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


// EDIT: I've implemented kirty's suggestions (in the comments) and centered the Thank you text, as well as added code that disables the submit button until a rating is chosen. Thank you kirty! ❤️

Hi!

This is my very first, ever, project that I've done fully on my own.

I've used ReactJS and Sass to build this component.

I definitely think I didn't use Sass to the fullest, however it was my first time using it, so I've used variables and nesting. Any feedback in regards to making the css file smaller are welcome.

I am also aware that I could have split the CSS styles for each component, however having looked into that, I would have to work with importing them, and I feel that this project is small enough it didn't warrant splitting the files up.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • kirty•380
    @kirtymeena
    Posted about 3 years ago

    Hi, nice work completing this challenge. I have noticed few issues:

    1. Thank you text is not in the center.
    2. user should not be able to submit without selecting a rating, I am able to submit which I think is not correct. You can create a form and use onSubmit to check if the user has selected any number or not.

    if you add the flip card effect on submitting it will look even better. Adding an active selector to a button makes it look nice when clicked on it.

    apart from small issues, the design looks good just thank you text and text below it are not centered.

    Keep coding.

    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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub