Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive Time Tracking Dashboard Using HTML,CSS,JS along with JSON

accessibility, semantic-ui
KrishnaPoddar1•400
@KrishnaPoddar1
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?

Utlizing the JSON file to get data for the first time.

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

Using JSON was really difficult and took a lot of research to get through

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

As you can see in the JavaScript Code I have some comments in nextFunc() which were not giving the proper output like:

const val = timeframes.${clickedId}.current; const value = element[val];

This is giving me undefined output and due to that I had to use a brute force method. I would love to know what was wrong in this and any other advice /suggestion will be helpful

This was my first time using JSON so I don't know whether it is correct or not.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jim Barnett•260
    @jamesbarnett
    Posted 11 months ago

    Just finished this challenge, so I was very curious to see another implementation. Your unit selection is fantastic. Refreshing to see no inappropriate uses of pixels. I also like how your solution does not use excessive chaining.

    You ask about this line of code: const val = timeframes.${clickedId}.current; const value = element[val];

    I can tell you are trying to use clickedId to select the appropriate data. But you cannot use the ${..} outside of a backtick delimited string. You found the correction to use the [] brackets instead and used that in your code, that's great. On the second statement, I think maybe it should change to const value = element[clickedId].current; I might be missing something.

    Great job getting this working. It's challenging!

    Hope this helps. Happy coding!

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