Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

responsive basic calculator built with react and tailwind css

tailwind-css, react
Ohootu jubelo•70
@jubelo1234
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. How did you deal with the numbers overflowing its container
  2. How did you perform your calculations
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ibukun450•390
    @Ibukun450
    Posted over 1 year ago

    Wow i am really impressed by this project keep it up

  • Mcnafaha•240
    @TheMcnafaha
    Posted over 1 year ago

    Nice job @jubelo1234!!!

    You manged to create a very useful and good looking calculator. In fact, it's so good that I'm not sure what your two questions mean since it seems to me that you have already found solutions to those two problems.

    One, you have added the over-scroll scroll for the display to handle numbers overflowing the display. This is the exact same thing I did.

    Two, you calculator functions according to arithmetic rules. It seems you used a combination of your own code for the user input and a math library to parse the user-made string. In my version, I had to (through multiple trials and errors) come up with my own function that does the same thing as evalute does for you.

    The only problem that I could notice with your calculator was that it currently has no way to handle someone spamming an operator. For example, if I click on the "+" key multiple times, I get "+++++" which is not what should happen. See example here.

    Luckily, thanks to your wise use of React's reducer, this is very easy to fix since your operator logic is easy to read and change.

          case "operator":
            const optr = `${action.payLoad}`;
            // this is first part of the code that I added
            const isOperator = /[.+/*]/.test(
              state.dispaly[state.dispaly.length - 1],
            );
            console.log("this is an operator ", isOperator);
            if (isOperator) {
              return { ...state };
            }
            // this is the last part of the code that I added
            return {
              ...state,
              dispaly: state.dispaly.concat(action.payLoad),
              show: state.dispaly.concat(optr),
              err: "",
            };
    
    

    With that code added, your app only accepts one operator at a time. Feel free to ask any questions about any part of the code above. Do note that it is still possible to spam the "." operator with my solution (see the second image here). As always, feel free to reach out if you want to explore a solution to that problem together.

    Can't wait to see what you code next, Best of luck!!!

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 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

Oops! 😬

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

Log in with GitHub