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

Mortgage Repayment Calculator using React Tailwind TypeScript

react, react-hook-form, tailwind-css, typescript, zod
P
Kamran Kiani•2,780
@kaamiik
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?

Proud of: Successfully integrating React Hook Form, Zod, and TypeScript to create a robust, type-safe form with clear validation and error handling. Do differently: Explore more advanced form management techniques, such as dynamic form fields or multi-step forms, to further enhance user experience.

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

Challenges:

  • Handling form validation for numeric inputs from native HTML inputs (which return strings).
  • Ensuring type safety between form inputs and business logic.

Overcame by: Using Zod to validate and transform string inputs into numbers, and leveraging TypeScript to enforce consistent types across the application.

What specific areas of your project would you like help with?
  • Optimizing the performance of form re-renders with React Hook Form.
  • Improving accessibility for native inputs and custom components.
  • Exploring best practices for integrating Zod with complex form structures

Feel free to share any additional thoughts or suggestions!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Wendy•2,150
    @wendyhamel
    Posted 3 months ago

    Hi there @kaamiik!

    Nice solution again here. The code looks good, it works smoothly and matches the design.

    I found a few small things you that could improve your solution. The border of the 'Mortgage Type' radio select dots is lime on a selected option in the design and the dots in your solution look a bit off center. The last issue I found is that if you click the 'clear all', the validation message of the 'Mortgage Type' shows up.

    I like the dotted outline you added on focus. It makes the focussed element stand out better than the focussed state from the design.

    Happy coding!

    Marked as helpful
  • P
    Andrey•4,320
    @dar-ju
    Posted 4 months ago

    Hi Kamran Kiani!

    Review as part of Learning Path.

    Excellent work! Everything works correctly and is done according to the layout.

    • I only saw a few errors in the html code that need to be fixed. The code needs to be checked before the build. Yes, if you use assemblers and frameworks, then it is difficult to get to the code. I use console.log(document.documentElement.outerHTML); in the browser console. Then, I check the resulting code in the validator.
    • There is also no limit on the input data, with large numbers you can get £NaN.
    • Usually, cursor pointers are not placed on input fields, this can be confusing. Pointers are for buttons and links.

    Good luck with your development!

    Marked as helpful

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.

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