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

Time Tracking Dashboard with Grid

fetch
Julianna Messineo•290
@mathematiCode
A solution to the Time tracking dashboard 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 proud of fetching and using the data from the JSON file. I needed some help to figure it out, and I'm not sure I could do it again without looking at what I did, but I understand it a little better. I'm also proud of how my website was easily responsive to different screen sizes with this line of code on my container in CSS

grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));

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

I was having issues with fetching and then using the data before it was fully fetched. I had to get help and learn where I could put my function within the .then function so that it wouldn't run until the data has been fetched.

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

Chat GPT gave me the suggestion to use this code:

fetch("./data.json")
  .then((res) => res.json())
  .then((data) => {
    timeData = data; // Assign fetched data to timeData
    fetchTimeDaily(timeData); // Call your function with timeData after it's fetched
  })
  .catch((error) => {
    console.error('Error fetching data:', error);
    // Handle errors here
  });

and it fixed all of my problems but I'm still not completely understanding why. Wouldn't the computer try to execute fetchTimeDaily(timeData) before timeData is set equal to data if this takes a little longer and they are both inside of the same .then statement?

Would it be better practice to do

.then((data) => {
    timeData = data; // Assign fetched data to timeData
}
.then (not sure what syntax goes here??)
    fetchTimeDaily(timeData); 
  })

 to make sure it waits until the first line has been fully executed?
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 Julianna Messineo'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.