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

Age-calculator-typescript-scss-jest

jest, react, sass/scss, typescript, vite
Teodor Jenkler•4,040
@TedJenkler
A solution to the Age calculator app 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 this project because I initially attempted it 8 months ago and had a really hard time understanding time calculations. All those Codewars and Exercism challenges seem to have paid off. Next time, I’ll focus on improving accessibility and SEO. I plan to read more on those topics and work on areas where I’m currently weak or less passionate.

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

The hardest part of this project was dealing with the configuration. I was also unsure about the best way to test my code. However, I’m pretty happy with my test coverage and believe I have tested all functionality thoroughly.

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

I would love feedback on the following specific areas of my project:

Jest: Any suggestions for improving my test coverage or test strategies?

SCSS: Advice on optimizing or improving my stylesheets and their structure?

TypeScript: Recommendations for better type management or any potential improvements?

Additionally, I implemented a feature that replaces form validation with auto-correction. For example, if a user types "31 February," it auto-corrects to the last day of February for that year, adjusting for leap years as needed. While I considered adding validation for the correct format, it feels unnecessary with the auto-correction in place. What are your thoughts on this approach?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Teodor Jenkler's solution.

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.