Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

React.js Responsive Mortgage Calculator App

react, vite
Elizabeth Sotomayor•230
@elizabethrsotomayor
A solution to the Mortgage repayment calculator challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm most proud of working with a new framework (React.js) and learning more about CSS selectors like ::before and ::after. Going into this project, I had some familiarity with React but had not tried building a project on my own so this was a great way to brush up and learn some new skills. Next time I would try to better plan out how the app would be structured because I had an idea of how everything would work together but didn't fully write out my plan.

What challenges did you encounter, and how did you overcome them?

A major challenge I encountered was with managing the state in both the and components. In order to fetch the values inputted into the calculator, I had to handle the state in the parent component (``) and pass both the values and set state functions as props to the child components. Using the React documentation helped illustrate this concept more clearly and helped me understand how this is implemented.

What specific areas of your project would you like help with?

I would like help with rendering custom error states as shown in the mockup. I made the input fields required but aside from that it doesn't change the color of the labels when a field is empty.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fernando A. Malfavón•370
    @Wlfernando
    Posted 9 months ago

    it depends how deeply you want to implement the solution. An easy try is use the pseudo-class :user-invalid. This one works with those that need to be filled, but not like radio or checkbox. Other is to retrive the value of validationMessage using useRef and update the state of the field with validitySate (https://developer.mozilla.org/en-US/docs/Web/API/ValidityState). Or use the library react-hook-form, I never use it but I heard is fine.

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