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

Responsive Advice Generator

P
Natalie Smyth•340
@nataliesmyth
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had some issues using the API in this project. By using the console, I can see that my code is fetching the data when the page loads or the dice icon is clicked, but the advice fetched only changes once every few minutes, and I'm lost as to why that is. Any advice would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roksolana•910
    @RoksolanaVeres
    Posted over 1 year ago

    Hi, Natalie! I have the answer to your question. The problem is in the very API, it takes a different amount of time to fetch data depending on the browser. And if you can generate a new piece of advice in Chrome every 2 seconds, in Firefox, for example, it takes an eternity to get another advice. One of the ways to overcome this issue is to modify your fetch request in this way:

     var response = await fetch("https://api.adviceslip.com/advice", {
        method: "GET",
        mode: "cors",
        cache: "no-cache",
      });
    

    Hope it helps and happy coding 🙂

    Marked as helpful
  • Bryan Li•3,530
    @Zy8712
    Posted over 1 year ago

    Your site looks pretty good. Not too sure what you mean by "advice fetched only changes once every few minutes", as I tested your site and it works as intended.

    One thing worth mentioning though is that its stated on the AdviceSlipAPI website that: "Advice is cached for 2 seconds. Any repeat-request within 2 seconds will return the same piece of advice." This might be what you mean by advice only changes after x amount of time.

    Hope this helps 👍

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub