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

Tip_calculator_app - HTML/CSS - JavaScript - SASS

sass/scss
JB•80
@JB-Doffemont
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Tried to practice SASS for the first time. My js does the work but I don't think is optimal.

I'll be grateful on any feedback on best pratices :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Darko•980
    @dtomicic
    Posted over 3 years ago

    I've taken a look at your JS and I would recommend you trim it down a lot since there's a lot of code that could be done simpler. I've done it by having the reset button reset all the values to zero, then I have a function that calculates the tip and the total amount in which I've selected all of the tip buttons with the class and I have a simple if/else if going through the array with classes, then for the total amount I just took the amount of the bill divided by the number of people and add the tip onto that.

    I've managed to do it in 127 lines of code compared to your 216 lines. You can take a look at my Github to get the idea and it might help you a bit. Since the more code you have easier it is to get lost in it and something not to work haha.

    I also see that your calculator doesen't recalculate on tip change (say you put 100$ bill with 5 persons and you put 5% and it calculates good but then you want to change the tip to 10% it doesen't recalculate because your probably listening only for change on bill and person input, you should change that).

    Also I would recommend not to reload the document every time you click reset, you could just set the values of the field to empty and set the rest of the values to 0.

    And this is not a big problem but you could try to fix it to practice your JS, when you get to really high numbers the amount just displays zero so try to play around with that ;)

    You should also look into fixing the design and making it more responsive, I'd recommend getting rid of the media query with max-height and width property and instead just make a box and put a max-width on that box and make a media query with min-width of 1440px for desktop design and then just widen the box a bit and it should look good since now its good up to 376px then it all gets pushed together and it's unuseable until after 1200px so I would recommend taking a look into that.

    I'd be glad to give you a hand if you're stuck somewhere so feel free to reply to this comment or get in touch with me somehow else (you can check my Github for my contact info) and I'll gladly help you out with your problems, take care :D

    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