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

Card component with using fetch API

Shuaib•640
@JustShuaib
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 actually finished the project for a while but I wasn't quite sure of my solution so I didn't post the solution. I stumbled across the solution and I felt I could give it some more touch, so here it is. Feedbacks are highly appreciated. 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ivan•2,610
    @isprutfromua
    Posted over 3 years ago

    One more thing: you are not catchnig an await errors, if server is down or smthing like this. Please handle it inside try / catch

    Marked as helpful
  • Ivan•2,610
    @isprutfromua
    Posted over 3 years ago

    Hi there. You did a good job 😎

    keep improving your programming skills🛠️

    your solution looks great, however, if you want to improve it, you can follow these steps:

    ✅ animation looks broken. Keyframes should looks like this

    @keyframes slidein {
      0% {
        opacity: 0;
      }
      100% {
        opacity: 1;
      }
    }
    

    ✅ move function declaration outside of the eventlistener adding

    dice.addEventListener("click", function () {
      async function getAdvice() {
        const adviceObject = await fetch("https://api.adviceslip.com/advice");
        const realAdvice = await adviceObject.json();
        const { advice, id } = realAdvice.slip;
        adviceText.classList.add("animate");
        adviceText.innerText = `"${advice}"`;
        adviceId.innerText = `#${id}`;
      }
      getAdvice();
      adviceText.classList.remove("animate");
    });
    

    ✅ don't use tag selectors. When you add CSS directly on tags, your markup can’t change. Your style is tightly coupled to your DOM, and any change increases the risk of breaking things.

    h1 {
      color: hsl(150, 100%, 66%);
      letter-spacing: 3.5px;
      text-align: center;
      font-size: 0.8rem;
      padding: 1.5rem 0 1rem 0;
    }
    p {
      text-align: center;
      font-size: 1.75rem;
      font-weight: 800;
      color: hsl(193, 38%, 86%);
    }
    
    

    I hope my feedback will be helpful. You can mark it as useful if so 👍

    Good luck and fun coding 🤝⌨️

    Marked as helpful
  • Shuaib•640
    @JustShuaib
    Posted over 3 years ago

    Thank you so much Ivan, I really appreciate you taking your time and going through my code. 😊 For the animation, I actually saw it on MDN used that way, that was why I used it. But I've changed it.

    By moving the function declaration outside the event listener, you mean I should define the function elsewhere and call it inside the event listener right? I'll handle the errors now too. I didn't think of it while implementing the code😄 I really appreciate your feedback and I'm definitely upvoting!

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