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

React Calculator (useReducer, Chakra UI, TDD)

accessibility, chakra-ui, jest, react, react-testing-library
Aman Singh Bhogal•1,010
@asbhogal
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Overhauled the UI design to something more minimalist and modern. The functionality and logic of the build remains the same (calculator operations, theme switching etc.) however here the themes are a light mode, dark mode and blue mode (using monochromatic color.)

Additional Features:

  • Ability to see previous operands added (including digits and operations)
  • Browser preference-detection (if the browser prefers dark-mode, default to theme 1 on page render, and if the browser prefers light mode, default to theme 2 on page render.)
  • Ability to use keypads on keyboard to enter digits and operations
  • useReducer to handle state within the application, with individual actions for typical calculator functionality via switch cases
  • Test Driven Development using Jest and React Testing Library as also been used - with unit testing for several edge cases against the Calculator and App component.

Styling

  • Chakra UI has been used to style the components, with custom component variants used to couple the styling with the JSX markup and theme extensions (see config file.)
  • Inter font (weights 400, 500, 700) for a clear, modern, clean and affirmed typography with accentuated x-heights for improved readability with mixed-case and lower-case text

Linting

  • ESLint

Lighthouse Scores: 99 | 100 | 100 | 100

Planned Iterations:

  • Apply the calculateScale() function to the currentOperand after the evaluate() function has been parsed (via ACTIONS.EVALUATE)
  • Resolve issue with scaled down currentOperand string values overflowing in parent container (a scrolling functionality has temporarily been incorporated here with custom styling)
  • Add smooth slide transitions between theme toggling
  • Add further edge cases for reducer functions and DigitButton and OperationButton components

Comments, suggestions and opinions welcome.

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 Aman Singh Bhogal'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.