Mortgage Repayment Calculator using React Tailwind TypeScript

Solution retrospective
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!
Please log in to post a comment
Log in with GitHubCommunity feedback
- @wendyhamel
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@dar-ju
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 - 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
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