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

Interactive Rating Component using Bootstrap 5 and JQuery

bootstrap, jquery
Hamsalekha•90
@LekhaKumar
A solution to the Interactive rating component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have several questions, and I am open to any tips and hints so that I can implement these tips in my future project.

  1. In the Javascript (I used JQuery) section, I used switch statements to change the value of the rating. I added the value attribute for each button, but I am unsure how to call the value in the JQuery (click function) instead of writing a bunch of switch statements.

  2. I tried to create a function for the clicking event for the rating section and call the function in the to submit button click function, but it is not working. So, I had to write the rating click function separately to make the code works. Can anyone explain why creating a function inside a function doesn't work?

ps: If my question is unclear, please let me know how I can explain it better. As I cannot show the code snippet here, I tried to write the question as clearly as possible. But, I understand that some parts of the questions may not be clear to the readers. Sorry for the inconvenience caused.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Divine Obeten•2,415
    @Deevyn9
    Posted almost 3 years ago

    Hi congrats on completing this project, it looks amazing and the logic works well. However, you can give the body a min-height of 100vh, a width of 100vw then you give it a display: grid; and then you place-items: center to center the container. Also, when the buttons are clicked, the button color isn't active, it appears and leaves immediately. Look into fixing these issues.

    I hope you find this helpful.

    Happy coding!

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

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