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

Time Tracking Dashboard

P
yinnie•320
@wcyin9
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I am unable to loop over each class; I am only able to change the first of type upon clicking. I understand that querySelectorAll should be used with forEach, but I am unsure how to include it with my current code. I am still learning JavaScript so I need a lot of guidance. Please correct my mistakes and let me know what else I can do to make it work

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alberto José•630
    @alberto-rj
    Posted 12 months ago

    👋 Hi yinnie, good to see you back solving the challenges!

    👏 Congrats on your solution, I found your code very easy to read!

    Why this is happening

    On line 24 to 26 of your script.js file, using the document.querySelector() method, you are only getting the first h2, .hours and .prev elements of the DOM.

    My suggestion for the problem

    Step 1: Starts at line 5 of your script.js file, get the six cards of the DOM.

    // card containers
    const workContainer = document.querySelector(".workContainer");
    const playContainer = document.querySelector(".playContainer");
    const studyContainer = document.querySelector(".studyContainer");
    const exerciseContainer = document.querySelector(".exerciseContainer");
    const socialContainer = document.querySelector(".socialContainer");
    const selfCareContainer = document.querySelector(".selfCareContainer");
    

    Step 2: After that, create a cards object, where each key is associated with the title of each card.

    // card map
    const cardMap = {
      "Work": workContainer,
      "Play": playContainer,
      "Study": studyContainer,
      "Exercise": exerciseContainer,
      "Social": socialContainer,
      "Self Care": selfCareContainer
    };
    

    Step 3: To work as expected, your updateTime function must be implemented as follows:

    function updateTime (timeFrame) {
      // getting JSON
      fetch("data.json")
      .then(response => response.json())
      .then(data => {
        data.forEach(value => {
          // store json data in variables
          const current = value.timeframes[timeFrame].current;
          const previous = value.timeframes[timeFrame].previous;
          const title = value.title;
    
          // get the card container by title
          const cardContainer = cardMap[title];
           
          // get the children of the card container
          const titleElement = cardContainer.querySelector("h2");
          const hrElement = cardContainer.querySelector(".hours");
          const prevElement = cardContainer.querySelector(".prev");
         
          // populate the children of the card container
          titleElement.innerText = title;
          hrElement.innerText = current + "hrs";
          if (timeFrame == "daily") {
             prevElement.innerText = `Yesterday - ${previous} hrs`;
          } else if (timeFrame == "weekly") {
             prevElement.innerText = `Last Week - ${previous} hrs`;
          } else {
             prevElement.innerText = `Last Month - ${previous} hrs`;
          }
        })
      })
     .catch(err => console.log(err));
    }
    

    Final words

    Note, there are many other ways to approach this same problem. I chose this way because I thought it would be the easiest to understand. If anything is unclear, or if you have any questions, let me know. It would be a pleasure to exchange ideas.

    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