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

Vintage Calculator of your dreams! (with react, typescript, sass)

react, typescript, sass/scss
turtlecrab•550
@turtlecrab
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Kinda proud of this one. In the previous challenge I encountered strange(for me) behaviour of type=number inputs with react+ts, and this time I decided to do all validations manually. It ended up pretty wild, I basically hardcoded every button's behaviour in every situation following my idea of how a real calculator should behave. I like how it came together, this is not the code to be proud of, but it does the job well! I could find only one sequence of actions that lead to NaN on the calculator screen, and it's not a straightforward one(can you find it?)

The stuff I wanted, but failed to implement:

  • Make screen overflow to the left and stay aligned to the right when there are lengthy numbers. It's working now with justify-content: flex-end but for some reason it's not scrollable with flex. Without flex, overflow: auto does it's job, but it overflows to the right despite that the content is aligned to the right. I tried approaches with direction: rtl - no luck, I tried scrollIntoView - it kinda does the job, but it also scrolls vertically and that's bad UX in my opinion. I went with flex in the end.
  • Issue related to the previous one - what to do with number with a lot of digits? Given that I chose flex with no scroll I decided to round decimals to 12 digits so a number like 0.333(3) is visible on the screen. It doesn't work for big numbers but it's something. I also made the screen expandable into two lines when there are long numbers, not sure about this decision.
  • How to handle all ⌨keyboard 👇events of the whole page? Now keyhandler is on the main div, but if we click away it loses focus. We can't put a keyhandler on the body, can we?

That was a great challenge which I really enjoyed, I appreciate any feedback!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on turtlecrab'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 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.