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

Interactive Rating Component using HTML, CSS and JS

Wesley•330
@wesleyjacoby
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This one was really difficult. Took me around 2 days to complete. Depressing, I know. It was my first time using JavaScript in a challenge.

I don't know if I did it right or not, but it seems to work. I'm finding it difficult to ask specific questions as I don't know if what I did is even correct? If you have any tips or suggestions, please let me know!

I appreciate it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hello Wesley, congrats on finishing the challenge! your app works perfectly and has the proper checks for the submit button

    Don't feel overwhelm in your first JS project, the important thinks when learning a new technology or programming language is to get it to work, doesn't matter if it's spaguetti code or not, is your first project and it works so the job is done!

    Your JS looks pretty good structured and you are using loops and if checks impresive for a first Javascript project IMO. You could have use a forEach loop to make it a bit more clear instead of a for of loop, wich actually is faster but less readable, for example something like:

    form.addEventListener('submit', function (event) {
        event.preventDefault();
        radioButtons.forEach((button, index) => {
               if(!button.checked) return;
                rating.append(button.value);
                mainContainer.classList.add('fade-in');
                innerContainer.classList.add('hide');
                innerContainer2.classList.remove('hide');
         })
    })
    

    Instead of checking it is checked, you can check if its not checked and instantly return, at the end is the same thing, also removed the console.log

    You can see that the differences are minimal, consider that I did write this code just here in this comment and didn't check the functionality!

    Hope my feedback helps you, keep going with those JS challenges!

    Marked as helpful
  • Enmanuel Otero Montano•2,155
    @Enmanuel-Otero-Montano
    Posted almost 3 years ago

    Hello Wesley!

    Congratulations

    Your solution for this challenge is correct, there are other ways to do it, but yours is also valid. Now you can look at other solutions to this challenge from other colleagues and you can compare and learn. Keep practicing with JavaScript and it will get easier and easier

    For the depressing and difficult don't worry, that will also help you deal with the frustration, very present in programming.

    Note: I have been up to 25 days to achieve a solution.😂😂😂

    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

Oops! 😬

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

Log in with GitHub