Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Interactive Rating Component using Sass and JavaScript

sass/scss
Nicholas Albuquerque•270
@nicoams
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there!

I added a validation to the form. It was not required but I wanted to explore some contents I learned while doing this and it worked.

I wrote down about my difficulties doing this project on the read.me file because I felt there I had more space to talk about it, I would be glad if you guys could check them. But to summarize:

  • I want to display a message if there is no option selected when submitting the form. Visually speaking is it better to: just push it into the container and let the flexbox do its magic or create a container big enough so it won't redistribute its elements?

  • I had to do a "magic number" kind of solution to hide the radio input on the Thank You Card. I used the innerHTML from JS to export the chosen option to that span, but since I put the input inside the label, the output contains an option (because that exported the button itself without css styles). I had to hid the input with something like input {display: none)} so it would hide the radio input but keep the label text. Is there a better way to this?

  • And this one is about some other thing I wanted to implement on this project but I did not know how to do it, so I need some help on this. I wanted keybord users to send the form as well. I do not know how relevant is this, but I thought it would be a nice touch (since we can usually type someting and press enter when filing a form). I have tried out some things but it did not work, so I left it out of the submission.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Nicholas Albuquerque's solution.

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.