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

Interactive rating tool using Semantic HTML, Sass and TypeScript

semantic-ui, typescript, sass/scss
Amélie•330
@aweliego
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


First challenge here - I like that it was a fairly simple app which also gave me room to use Sass and TypeScript for the first time outside of course guided projects. Helped me consolidate stuff like fading in elements with CSS transitions too. I'm still trying to get the hang of TS, it's really hard for me to understand how it benefits the code at times, and I feel like most of the TS code I wrote was because TS "made" me by showing errors if I didn't. Haha. But given the amount of code in this challenge, maybe using TS (and Sass) was a bit of an overkill. Anyway, fun little project.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Amélie, well done completing your first challenge here at Frontend Mentor, and a warm welcome to the community 😊

    I agree that sometimes it seems like an overkill to use tools and libraries for these little components; having said that, I also agree with the point you made about how this gave you the opportunity to use what you learned. I think that's probably more important in the long run because chances are you might have to build components like these with TS as part of a larger project later, so it's worth the practice!

    About this component, one suggestion I have is to see whether you can put in some logic that prevents the user from proceeding to the thank you page if they don't select a score; right now, when I click on submit without selecting a rating, I'd get "undefined" in the message, and so it would be good if the user doesn't have to see that.

    Once again, great work, and I enjoyed reading about your reflection on the whole process. Keep going! 😊

    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