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

Mortgage Calculator using react-hook-form and TypeScript.

next, tailwind-css, typescript, accessibility
Tesla_Ambassador•3,070
@tesla-ambassador
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 mostly proud of the fact that I got to learn how to use the react-hook-form and also completing this project while using TypeScript for the first time with Next.js.

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

I explained all these details in my README.md file

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

Mainly accessibility and better coding practices when using Next.js/React.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • qadzek•580
    @qadzek
    Posted 9 months ago

    Well done, impressive work!

    TypeScript can be annoying indeed but it catches so many bugs. If you have trouble finding the TypeScript types, hovering over them in VS Code in the right place should reveal them.

    Congrats on implementing the comma separator, I skipped over that part.

    Possible improvements:

    • The interest rate input field should accept all floats, e.g. 4.9.
    • Don't use HTML like <br /> in Markdown.
    • Try using template literals (backticks) instead of spanValidClass and spanInvalidClass, to avoid duplication.
    • Intl.NumberFormat might be helpful.
    • Clicking on the far end of the box containing the radio button should work.
    Marked as helpful
  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted 9 months ago

    Broooooo

    I've just seen this!!

    Nice work dude! 😎 Your solution looks great and I loved reading your README 😂 You put a lot of thought into this and that's how you learn the most!

    Keep on grinding my guy and happy coding!! 😁

    EDIT: I'm touching grass these days... whenever I can 😜

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub