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

Interactive rating component solution

accessibility
John Alvin•100
@VincC2312
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello guys,

This my solution for Interactive rating component. I'm still struggling with JavaScript because I'm having a hard time to write simple codes. 😅 I watched some tutorials and courses, I fully understand the theory but when I'm starting to build some simple project I'm still struggling with it. I do know the usage of each tools but I don't know how to apply it fluently. 🥲

Thanks guys in advance for any feedback, tips and advice. 😀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amélie•330
    @aweliego
    Posted almost 3 years ago

    Hi John,

    Well, from what I can see your code looks very neat, DRY and accessible, so well done! Regarding what you mentioned about struggling to write 'simple code': totally normal when you're starting out. I would say, don't worry about your code looking very efficient and DRY at the beginning, just focus on making the app work. Once you have that done, you can focus on refactoring and it should be easier then to see what you can bundle together or separate into different functions etc. It takes a lot of trial and error and there are also so many ways you could have built this app with vanilla JS, there's not just one right way to do it. Anyway keep at it, the more practice the easier you will find it to get into the implementation of the features :)

    Nice that you used Sass (you should add it to your readme!) and I actually thought it was quite creative to increment the index of the score by 1 to get the right value. Also great that you thought of the disabled attribute for the submit button.

    Design-wise, your solution looks a bit more 'compact' than the original, I would perhaps add some spacing/padding.

    Regarding your JS, just two small comments:

    • There's a bit of a mix of ES6 and older syntax in your code, I would standardise everything to arrow functions
    • Instead of naming your variable rateBTN, I would name it rateBtns - it's best practice to use camelCase and since this refers to multiple buttons, it would make your code more readable to make it plural :)

    Happy 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