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

tip calculator made with react, sass and packed with vite

react, sass/scss, vite
Luis Jimenez•760
@LuisJimenez19
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


App created with react and vite, using the 3 main hooks and styles with sass to be able to use the variables, use the props to be able to give the styles to the buttons, but use the useContext to be able to give the functionality to the app, the correct thing should be It would have been to use the context for everything, but since I'm practicing, my biggest question is to know if there is another way to give the styles to the buttons in a more optimal way

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • yishak abrham•2,150
    @yishak621
    Posted over 2 years ago

    Congrats for completing the challenge but the card is not responsive to mobile the fonts are squashed so work on that ....it should be displayed as a design image ...when we come to the functionality the event is not fired unless the user come back to the tip percent buttons in ur design .....but it should be fired .....1]when a user type the value in number of peoples input .... 2]when a user come back to the tip percent buttons and click the btns and also type in to the custom input So to enable that type of events u should use input events or keyup events that allows the events to be fired automatically when a user types input and also the should not be 0 error message should be fired when a user types 0 value ...it shouldn't be fired when a user click on the percent buttons ...so use if conditional statement to restrict that event

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub