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

Age Calculator using Javascript date object

accessibility, pure-css, van-js
Chinemerem Ugbaja•200
@marycynthia2020
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?

In the course of building this project, I learnt about the inbuilt JS date fucntion. Throughout this project, I worked with Date function. It is really an opener. Building this age calculator, I must say improved my logical thinking when it comes to JS, looking at a problem and analysing it. I beleive building more projects like this will help me as I continue in this journey

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

This project challenged me so much when it comes to input validation and writting a DRY code. I dont know if I have ever written a code as DRY as this before. The validation wasn't easy at all. I ended up with lots of conditions that made the code tacky. Modifying the code into what it is now, I must say was really challenging for me. But I am happy I did it finally. I so much appreciate Andrew Ezeani who came through for me when it seems everything wasnt working again.

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

I would appreciate suggestions on how I can write a better and DRY Javascript code especially in the input validation aspect.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Chinemerem Ugbaja'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 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.