Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

Interactive rating component SASS and EDA

sass/scss
nodegreecode•390
@nodegreecode
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

This time, I focused on organizing my app’s logic and exploring new architectural approaches. I found two suitable solutions for a small project like this: Module Architecture using IIFE and Event-Driven Architecture (EDA) with an Event Bus, utilizing Publishers and Subscribers. Since IIFE is somewhat outdated, I chose EDA.

I had already worked with event handlers in my previous project, Tips Calculator, and wanted to deepen my understanding by applying them again.

In this project, I built a component that validates whether the user has selected a rating and displays an error message accordingly. After submitting a rating, I also implemented a return function that allows users to go back to the rating form. This feature is, of course, purely for practice within this project.

What challenges did you encounter, and how did you overcome them?

When it came to CSS, one of the challenges was styling the selected rating button—specifically, setting its background and creating the "glowing shadow" effect around the star.

In JavaScript, the tricky part was figuring out how to properly validate the radio inputs and reset the UI to its default state after "rerouting" back to the submission form.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Coder-Liz•610
    @Coder-Liz
    Posted 4 months ago

    Great job, the layout looks really good.

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