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

Advice Generator App using React, SASS/SCSS, Axios and Advice Slip API

react, sass/scss, axios
Melwyn•250
@melwynt
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The bigest challenge here was to retrieve a new advice on each new click on the dice. At first fetch or axios were not getting a new advice even though I was triggering a new request to the API url. This was due to fetch and axios caching data. To overcome this issue, the solution was to add a timestamp in the URL.

Overall I'm pretty happy of the outcome and it was also fun to great that glow effect when hovering the dice.

Hope you like this one!

I would be super grateful if you could follow me here or on Twitter @melwyncode

Thanks ❤️

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ian Muchina•140
    @ianmuchina
    Posted over 3 years ago

    Hello.

    One solution is to get an advice slip using it's id. eg: Get advice 100 by going to https://api.adviceslip.com/advice/100 Currently, the valid ids are those between 1 and 224.

    You can then generate a random number between 1 & 224 on the client side each time the button is clicked.

    Here's an example with fetch

    async function fetchRoll() {
       id = Math.floor(Math.random() * 224);
      
       // Get Remote Data
      let response = await fetch(`https://api.adviceslip.com/advice/${id}`);
      let data = await response.json();
    
      // Update DOM
      adviceId.innerText = data.slip.id;
      adviceText.innerText = data.slip.advice;
    }
    
    // When dice button is clicked
    dice.onclick = fetchRoll;
    

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