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

Calculator - ReactJS + styled-components

react, styled-components
Syed Ali Mansoor•460
@syedalimansoor
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone! 👋

Another project with React! This calculator was quite fun to make and I constantly ran into so many issues with each step. Fixed them all, though! 😁

This project was my first foray into CSS-in-JS and component-scoped styles. I originally started off with emotion since I read somewhere that it was more efficient than styled-components. However, as I developed the calculator, I found out that emotion re-renders components completely when dynamic props used in styling change. This was a problem as I couldn't incorporate CSS transitions when, for example, the background-color of a certain element changed, as the element was completely re-rendered.

After some research, I discovered that styled-components separates component classes into static and dynamic classes. When dynamic props change, only the dynamic class of a certain component changes instead of it being re-rendered. This naturally allowed for CSS transitions, and styled-components was thus a winner for me!

While developing the calculator, I started off with an approach that stored the calculator display state as a numerical value. However, this meant that I would have to define what the press of each key would entail for the display state, separately. This also meant that displaying values such as "0.04" and "3." would become impossible since the decimal point was removed when converting to a Number.

I, therefore, decided to store the display state as a String (for example, "12 + 0.3 / 2") and then let Javascript's eval function handle the calculation. I have read that the eval function can be dangerous to use, however. Do you guys have any other suggestions or replacements?

Any feedback on the app is highly appreciated, thanks! ✌

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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