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

Tip Calculator App using Tailwind CSS

tailwind-css
Javier Duarte•210
@javiIT10
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • mofada•340
    @mofada
    Posted 12 months ago

    Your JavaScript code is well-organized and structured. However, there are some suggestions for improving readability, maintainability, and efficiency:

    1. Optimization and Best Practices:

    • Debounce Input Events: Currently, the event listeners for input fields trigger calculations every time the user types something. To improve performance, especially with large inputs, consider debouncing the input event listeners.

      function debounce(func, wait = 300) {
        let timeout;
        return function (...args) {
          clearTimeout(timeout);
          timeout = setTimeout(() => func.apply(this, args), wait);
        };
      }
      
      inputBill.addEventListener("input", debounce(function () {
        values.bill = parseFloat(this.value);
        if (!isNaN(values.bill)) {
          calculate();
        }
      }));
      
    • Consistent Variable Naming: The variable alert can be confusing since it's a global function in JavaScript. Consider renaming it to something more descriptive, like alertMessage or alertElement.

      const alertMessage = document.querySelector("#alert");
      

    2. Maintainability:

    • Separate Calculation Logic: The calculate function is doing a lot of work. You could separate the logic for calculating the tip amount and the total amount into individual functions. This will make the code easier to test and maintain.

      function calculateTipAmount(bill, tip, people) {
        return (bill * tip) / 100 / people;
      }
      
      function calculateTotalAmount(bill, tip, people) {
        return ((bill * tip) / 100 + bill) / people;
      }
      
      function calculate() {
        const { bill, tip, people } = values;
        resultTipValue.innerText = `$${calculateTipAmount(bill, tip, people).toFixed(2)}`;
        resultTotalValue.innerText = `$${calculateTotalAmount(bill, tip, people).toFixed(2)}`;
      }
      
    • Reuse of CSS Classes: In the showAlert and cleanAlert functions, you're adding and removing multiple classes for styling. Consider grouping these styles into a single CSS class, like .alert-active, to reduce redundancy.

      .alert-active {
        border: 2px solid #CA8073;
      }
      

      Then, in your JavaScript:

      function showAlert(reference) {
        alertMessage.textContent = "Can’t be zero";
        reference.classList.add("alert-active");
      }
      
      function cleanAlert(reference) {
        alertMessage.textContent = "";
        reference.classList.remove("alert-active");
      }
      

    3. Error Handling:

    • Handle NaN in calculate: Ensure that the calculate function can handle cases where the input values might not be valid numbers (NaN). This can prevent unintended results being displayed.

      function calculate() {
        const { bill, tip, people } = values;
        if (isNaN(bill) || isNaN(tip) || isNaN(people) || people === 0) {
          resultTipValue.innerText = `$0.00`;
          resultTotalValue.innerText = `$0.00`;
          return;
        }
        resultTipValue.innerText = `$${calculateTipAmount(bill, tip, people).toFixed(2)}`;
        resultTotalValue.innerText = `$${calculateTotalAmount(bill, tip, people).toFixed(2)}`;
      }
      

    4. Reset Function:

    • Complete the reset Function: You have an empty reset function. Consider moving the reset logic from the btnReset event listener to this function for better code organization.

      function reset() {
        values.bill = 0;
        values.tip = 5;
        values.people = 1;
      
        inputBill.value = 0;
        inputCustom.value = 0;
        inputPeople.value = 1;
        resultTipValue.textContent = "$0.00";
        resultTotalValue.textContent = "$0.00";
        removeActive();
      }
      
      btnReset.addEventListener("click", reset);
      

    5. General Suggestions:

    • Avoid Global Scope Pollution: Consider encapsulating your code within an IIFE (Immediately Invoked Function Expression) to avoid polluting the global scope.

      (function() {
        // All your code here...
      })();
      

    By applying these suggestions, your code will be more efficient, readable, and easier to maintain.

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