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

HTML , CSS , Vanilla JavaScript and API calling ( using Fetch API )

fetch
Rachit Patel•540
@rachit0706
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Made some necessary changes after reading some wonderful feedback.

Any more suggestions for improvements will be welcomed :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nneoma Njoku•1,210
    @SatellitePeace
    Posted almost 3 years ago

    Hello @rachit0706

    I noticed that your button does not work and you can only get new advice when you reload the page

    • The purpose of the challenge is for the app to fetch new advice on click which means that button is meant to have an event listener that will call a function to produce new advise on click like in the example below
    btn.addEventListener("click", function () {
      advice();
    });
    
    • I also noticed that you used Math.random() which is not very necessary because the API in question is designed in such a way that it generates random advice each time you make a request

    • Also shortening the length of the advice kind of defeats the purpose except if you were using it as a way to learn something new

    • so a better solution might be to get the advice url to fetch it with any method you like in your case you used async/await, then extract the id and advise from the API and attach it to your main content innerHTML like so

    async function advice() {
      const response = await fetch(URL);
      const data = await response.json();
      const { id, advice } = data.slip;
      adviceText.innerHTML = `<h1 class="advice__heading">Advice # ${id}</h1>
            <p class="advice__text">
          " ${advice} "
            </p>`;
    }
    

    advice();

    • make sure you call this advice(); function inside your button event listener to make sure that each time the button is clicked new advice is fetched

    • In your html your dice img should be enclosed in a link tag

    I HOPE THIS HELPS

    Marked as helpful
  • Absorberend•390
    @Absorberend
    Posted almost 3 years ago

    Hey bro, looking good!

    I noticed that the button didn't work, you can add it with the code below if you like. I noticed you'll run into an error eventually with this code. I think it's because some advice statements are actually > 95 characters long and it gives an error. I'm not 100% on that.

    const  diceBtn = document.querySelector(".dice-img");
    
    diceBtn.addEventListener("click", async function() {
    
        let adviceData = await generateAdvice();
    
        theAdvice.textContent = `"${adviceData.advice}"`;
        adviceNum.textContent = `Advice #${adviceData.id}`;
    });
    
    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

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