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

Html, Scss, Javascript

lordag•240
@lordag
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Rahexx•960
    @Rahexx
    Posted 8 months ago

    Great job with this challenge!

    Your app looks great and works properly. Here are some suggestions to improve your code structure and readability:


    HTML & CSS

    1. Class Naming:
      Some of your class names are quite long. For instance, instead of container__form__item__tip__label, you could simplify it using BEM methodology by using block for form. For example:
      .form__item__tip__label
      This makes your code easier to read and maintain.

    2. Modular SCSS Structure:
      Consider organizing your SCSS files by creating a folder like components and moving specific styles (e.g., for the form) to separate files such as _form.scss. Then import them into your main.scss.

      • With nearly 500 lines of styles in one file, it's a good time to break it into smaller, reusable chunks for better maintainability.
      • You can also extract common styles, variables, and mixins into separate files.

    JavaScript

    1. Destructuring:
      In cases where you access object properties multiple times, you can use destructuring to improve readability. For example:
      const { bill, tip, number_of_people } = data;
      This reduces repetition and makes your code cleaner.

    2. Event Handling:
      Great job using event listeners to handle user input dynamically.

    3. Proxy Implementation:
      Using Proxy to handle state updates and validations is an excellent approach! This keeps your state management clean and ensures all changes go through a central handler.


    Final Suggestions

    • Extract reusable functions into separate modules/files for better reusability and testability.
    • Modularize your CSS/SCSS for easier navigation and maintenance in larger projects.
    • Keep up the excellent work with structured and clean JavaScript code! 🎉

    Good luck with your next challenges!

    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