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

Tip Calculator App

P
Hector Ramirez•450
@hectorlil48
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'm proud that I completed the project and figured out the JavaScript, even though I relied on a lot of help from Google along the way. There's still a lot for me to learn, and I want to keep improving my JavaScript skills so I can solve problems more independently in the future.

What challenges did you encounter, and how did you overcome them?

Sure! Here’s a more concise explanation of how you handled coding the error state: One of the challenges I faced was implementing an error state for the "Number of People" input before performing calculations. In the calculateAmounts function, I check if the input is empty or less than or equal to zero. If so, I set the outline color to red and displayed an error message, using return to prevent further calculations.

If the input is valid, I reset any error states, ensuring calculations are only done with valid data. This approach provides immediate feedback to users and enhances the overall functionality of the tip calculator.

What specific areas of your project would you like help with?

Need more practice solving problems with JavaScript. I intend to do more problem-solving.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Hector Ramirez's solution.

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
Frontend Mentor logo

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 1st-party linked stylesheets, and styles within <style> tags.

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.