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

Pricing Component using SCSS and Vanilla Javascript

Nicole•360
@nicole-tuznik
A solution to the Pricing component with toggle challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


No specific questions, but feedback is always appreciated! :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • tomthestrom•165
    @tomthestrom
    Posted over 4 years ago

    Hey Nicole,

    I was looking at your JS code. It's nice and readable, just a few things that are mostly a matter of taste.

    This whole code could be wrapped in an IIFE to avoid polluting the global namespace. It's a basic app and does no harm doing it the way you do, but it's a good practice to think if you really need to have globals before using them (build good habits from the beginning).

    let monthlyPrice and let annualPrice should be const, they are not reassigned anywhere.

    const toggle = document.querySelector("#toggle"); could be a getElementById, it tells better what you're doing since querySelector is more of a general tool.

    querySelectorAll based on class names are not the best, it's a better practice to use data attributes, again at this scale of an app it doesn't matter that much, just something to be aware of.

    toggle.addEventListener("click", function () {
      if (toggle.checked) {
        for (i = 0; i < annualPrice.length; i++) {
          annualPrice[i].style.display = "none";
        }
        for (i = 0; i < monthlyPrice.length; i++) {
          monthlyPrice[i].style.display = "block";
        }
      } else {
        for (i = 0; i < annualPrice.length; i++) {
          annualPrice[i].style.display = "block";
        }
        for (i = 0; i < monthlyPrice.length; i++) {
          monthlyPrice[i].style.display = "none";
        }
      }
    });
    

    This could be shortened for readability and to reduce repetitiveness to:

    toggle.addEventListener("click", function () {
        for (i = 0; i < annualPrice.length; i++) {
          annualPrice[i].style.display = this.checked ? "none" : "block";
        }
        for (i = 0; i < monthlyPrice.length; i++) {
          monthlyPrice[i].style.display = this.checked ? "block" : "none";
        }
    });
    

    You could also use Array.map() or Array.forEach() instead of those for loops to make it more declarative.

    Your github repo shouldn't include the .DS_Store file and the package-lock.json.

    Have a good day,

    Tom

  • Samuel Palacios•615
    @samuelpalaciosdev
    Posted over 4 years ago

    Hi, Nicole👋

    Well done on this challenge! Your solution looks good and it scales pretty well👍

    I only suggest some things 😉:

    • Adding a transition to the toggle. I'd add a transition: .5s; on the #toggle::after element, it make it feel more smooth.

    • You don't have a h1 on this project as it stands. Having your headings on order is not really a rule, but the h1 it's one of the most important tags on an webpage . For this project, it would be where you've got the h5 heading.

    I hope this would help you, have a nice day, keep 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

Oops! 😬

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

Log in with GitHub