Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Advice Generator App

vite, tailwind-css
AbalJerind•400
@Abaljerind
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud that I can finally implement how to use useState and useEffect using react in this challenge and it works.

What challenges did you encounter, and how did you overcome them?

It's quite hard to add customized styles to tailwindcss v4 here, but I manage to do it and it's actually quite short than v3.

What specific areas of your project would you like help with?

Perhaps with the styles, it's actually kind of difficult without the design numbers from Figma, so I just went round and round giving the styles and check it with the design but I'm completely blind with the numbers of the designs. Anyone can help?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jay Khatri•4,230
    @khatri2002
    Posted 5 months ago

    Hi @Abaljerind!

    The developed solution looks good!

    I would just suggest you to use a try-catch block in the handleGetQuote function, where the API is being called.

    async function handleGetQuote() {
      try {
        const res = await fetch("https://api.adviceslip.com/advice");
    
        // Check if the response is successful
        if (!res.ok) {
          throw new Error(`HTTP error! Status: ${res.status}`);
        }
    
        const data = await res.json();
        setQuote(data.slip.advice);
        setQuoteId(data.slip.id);
      } catch (error) {
        console.error("An error occurred while fetching the quote:", error);  //Can be removed in production environment
        alert("Sorry, we couldn't fetch a quote at this time. Please try again later.");
      }
    }
    

    Why is error handling important in API calls?

    1. Uncertain Server Responses: APIs can behave unpredictably. The server might be down, rate limits could be exceeded, or there could be unexpected errors on the server side. Handling errors ensures your app can gracefully deal with such situations.

    2. User Experience: Without error handling, your app might crash or display incomplete information, leaving users confused. A clear error message (like "Sorry, we couldn't fetch a quote") keeps the user informed.

    3. Network Issues: Network failures or connectivity issues can occur, especially in mobile environments. The catch block can handle these gracefully.

    4. Standard Practices: It's a best practice to handle errors where the API call is made. Centralizing error handling here ensures you're addressing failures close to their origin and maintaining cleaner and more maintainable code.

    5. Future-proofing: If the API changes its response structure, adds authentication, or modifies its behavior, proper error handling can prevent breaking your application. For instance, checking res.ok ensures that you're not blindly processing an error response as if it were successful.

    By wrapping your API calls in a try-catch block, you make your application more robust, user-friendly, and aligned with best development practices.

    The rest of the solution looks amazing! Keep up the great work! 🚀

    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