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

HTML 5, SASS, JS, JSON server

ThanhVuong0904•465
@ThanhVuong0904
A solution to the Time tracking dashboard challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


data in (db.json) Hope you like this solution. Please tell me if there is something to improve in my code. Thanks you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Faris P•2,810
    @FarisPalayi
    Posted almost 4 years ago

    Like @nmorajda pointed out, http://localhost:3000/tracking won't work. It is because localhost only works on the computer that runs the code. i.e. it won't work when you host it.

    Here, you don't need to use localhost. You can simply fetch the json file by using the fetch api to do the job. json-server package is unnecessary here because it is only/mostly used for creating REST api endpoints for quick prototyping and mocking, so that you don't have to write server side code only to create api endpoints.

    You can just rewrite the getData function in to this:

    const API = "db.json";
    fetch(API)
         .then(response => response.json())
         .then(({ tracking }) => callback(tracking));
    

    If you were trying to learn how to host server-side code, and used json-server because you don't know backend, then go ahead and host it on Heroku or Google App Engine or any other platform you like. Just make sure that, you replace the http://localhost:3000/tracking with the url that you have given by the platform (for example: http://project-name.herokuapp.com/tracking). And also don't forget to add the start command. If you are using heroku, you can specify that in the Procfile. If you are using GAE, you will need to specify the runtime also(for eg: nodejs14), in the app.yaml file, and it will automatically look for the start command in the package.json and runs it. Hope it all make sense. If not, feel free to ask me for clarification.

    • Also, you don't need to upload(to github) or track node_modules folder. Because, as long as the packages are listed on the package.json, anyone can use npm install command to install all the packages. To tell git to not track, add node_modules/ to .gitignore file.
    Marked as helpful
  • nmorajda•945
    @nmorajda
    Posted almost 4 years ago
                        if(clickIndex === "weekly") {
                             timeFramesCurrent = timeframes.weekly.current;
                             timeFremesPre = timeframes.weekly.previous;
                        }
                             
                        else if (clickIndex === "daily") {
                             timeFramesCurrent = timeframes.daily.current;
                             timeFremesPre = timeframes.daily.previous;
                        }
                        else if (clickIndex === "monthly") {
                             timeFramesCurrent = timeframes.monthly.current;
                             timeFremesPre = timeframes.monthly.previous;
                        }
    

    can probably be written shorter and just as legible:

    const timeFramesCurrent = timeframes[clickIndex].current;
    const timeFremesPre = timeframes[clickIndex].previous;
    

    or maybe:

    const {current, previous} = timeframes[clickIndex]
    

    in the second case you have to rename the variables later in the code or

    const {current: timeFramesCurrent, previous: timeFremesPre} = timeframes[clickIndex]
    
    Marked as helpful
  • nmorajda•945
    @nmorajda
    Posted almost 4 years ago

    Links don't work, I guess that's why:

    function getData(callback) {
       const API = "http://localhost:3000/tracking";
        ...
    

    and correct the errors visible in the report at the top.

    Happy codding :)

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

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