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

Responsive Mortgage Calculator

react, sass/scss
Quae03•110
@Quae03
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 proud of my use of useContext after realizing that prop-drilling was not the most effective choice for all the components in this project. I hit a brick walling trying to prop drill multiple variables across multiple components, but thats a good thing because we learn through failure

I would plan appropriately and map out the structure of my components

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

challenges: Prop-drilling not being effective for every component, getting used to making components as opposed to several functions in plain Javascript

I used useContext so I could import any component I want into any component necessary and broke down my application into small components to get used to using components

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

Modularity, some of my functions are not able to be exported and added to another project without additional code

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Jan Kotvaš•460
    @DrakeHermit
    Posted about 1 month ago

    Good job on finishing the project, it works as it should and that's all that matters. But that being said you didn't really follow the design file at all, and you should make it a bit more responsive, maybe on mobile devices let the content span the whole screen instead of having background color. I saw you included two h1's, in your markup, which is not recommended at all. Also I noticed you do div.[class] which is not necessary or section.[class] for that matter. Also when you want to destructure values or functions from context you made you can just do it in one line const {...} = useContext(ParameterContext) instead of destructuring each value on a different line. Also you don't need to e.preventDefault() in every if statement it's enough if you just include it at the top of the function. I suggest you go over the earlier learning paths and brush up on html, css, and js knowledge before you continue working with react. That's all if you want you can look over my github profile.

    Happy coding!!

    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 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