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

Interactive rating component

Nahuel-cell•220
@Nahuel-cell
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would really appreciate if you could give me feedback on my little project. The most difficult part of this was when I wanted to select another classification and make the orange color of the number go to the new element that the user clicked on. I don't know if I explained myself but I appreciate that you comment on my mistakes or improvements. Just judge for yourself and then tell me.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eileen dangelo•1,600
    @Eileenpk
    Posted over 2 years ago

    Hi Nahuel-cell, your project looks good.

    I would consider changing the let rating; to let rating = null

    It is generally considered good practice to initialize a variable with a value, rather than declaring it without a value. If you are declaring a variable with a type "let" or "const" and you're going to assign it a value later, it's a good idea to initialize it with a default value, like null. This is because, if you don't initialize a variable and try to use it before assigning a value to it, it will throw a "ReferenceError: variable is not defined" error. By initializing a variable with a default value, you can avoid this issue and make your code more predictable. Additionally, if you are going to use a variable in an expression, it's a good idea to initialize it with a default value that is appropriate for the expression, such as an empty string or zero. So, it is considered a good practice to initialize a variable with a default value, such as null, when you are going to assign it a value later.

    Hope you found this helpful!

    • Let's connect on LinkedIn! - @Eileenpk
    Marked as helpful
  • Dytoma•550
    @Dytoma
    Posted over 2 years ago

    Hey👋

    Good job on completing this challenge👏

    I have some feedback that you can use to improve your code:

    • First instead of using article elements, I will suggest you use div elements and give them a role attribute(eg: <div role="main">....</role>).
    • For the <div class="attribution">......</div> you can add a role="footer" you can learn more about landmarks here. And for <img src="./assets/images/illustration-thank-you.svg" alt="Illustration" class="article__illustration"> I will suggest you add an aria-hidden='true' attribute for screen readers to skip this image as it just serves for decoration.

    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 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

Oops! 😬

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

Log in with GitHub