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

Tip Calculator App

sass/scss
P
Emmanuel Lopez•550
@EmLopezDev
A solution to the Tip calculator app 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?

I am alway proud when I complete a challenge, not giving up is a big win for me. Other than that gaining a better understanding of how to work with numbers for calculations in JavaScript.

What challenges did you encounter, and how did you overcome them?
  • Converting the input values to numbers to calculate was tricky. I was originally using parseInt() but it was giving me issues at times, so I learned for my case it was best to use Number()
  • Also dealing with the arrows in the number input and their spacing, I learned there was way to remove them.
What specific areas of your project would you like help with?

Definitely the JavaScript. I would like feedback on what I have and if I could have made it more efficient.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Valeria Montoya•450
    @ValeriaMontoya
    Posted 3 months ago

    Hi @EmLopezDev 👋🏻

    Your JavaScript code is generally well-structured and understandable. However, there are a few areas where improvements can be made. Here’s a breakdown:

    Typo

    const addAcitveTip = (evt) => { ... }
    

    addAcitveTip should be addActiveTip.

    Repeated DOM manipulation
    You're calling tipButtons.forEach() multiple times in both removeActiveTip() and addAcitveTip(). These can be merged for better performance and clarity:

    const setActiveTip = (evt) => {
        tipButtons.forEach((button) => {
            const isActive = button.id === evt.target.id;
            button.classList.toggle("active", isActive);
            if (isActive) tipCustom.value = "";
        });
    };
    
    const addTip = (evt, value) => {
        setActiveTip(evt);
        tip = value ? Number(value) : null;
        showResults();
    };
    

    Inefficient showResults() logic
    You're checking the same condition twice with a lot of repeated code. Combine conditions using else and simplify:

    const showResults = () => {
        const errors = {
            bill: !bill,
            tip: tip === null,
            people: !people,
        };
    
        billErrorSpan.innerHTML = errors.bill ? "Can't be zero" : "";
        tipErrorSpan.innerHTML = errors.tip ? "Must select tip" : "";
        peopleErrorSpan.innerHTML = errors.people ? "Can't be zero" : "";
    
        if (errors.bill || errors.tip || errors.people) {
            tipPerPersonSpan.innerHTML = "$0.00";
            totalPerPersonSpan.innerHTML = "$0.00";
            resetButton.setAttribute("disabled", true);
        } else {
            const perPerson = formattedResults();
            tipPerPersonSpan.innerHTML = perPerson.tip;
            totalPerPersonSpan.innerHTML = perPerson.total;
            resetButton.removeAttribute("disabled");
        }
    };
    

    I really hope my feedback helped, keep 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

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