Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Advice Generator

gatsby, react, tailwind-css
Alex•100
@AlexDevOp4
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


During the project's development, I faced difficulties due to my limited recent experience with React and Gatsby. I had to refresh my knowledge and learn new concepts to effectively build the app.

As for the code, I don't have any specific areas of uncertainty. However, I might appreciate some guidance or feedback regarding the usage of React hooks in my codebase.

While I don't have any specific questions about best practices, I welcome any comments or suggestions you may have regarding the project's implementation.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Luna•40
    @CharlyLuna
    Posted about 2 years ago

    Hey, regarding to your code, I would add an useEffect to do the fetch from the API at the beginning so the user can see some text in the page in the first load, I think this can be a good user experience instead of seeing the empty text in the box.

    Also I would recommend if you want to practice a little more, using a custom hook so you can separate the logic from your component. You can have a file named useAdvice or something like that were you put all this logic:

    const [advice, setAdvice] = useState(null); // the advice is an object so you can put here null or a basic structure of how the object is: {advice: '', id: '0'}
    // const [isLoading, setIsLoading] = useState(true) *you can even add this state if you want to show a loader while the fetch is taking place
    
    // useEffect(()=>{},[]) *executing the diceRoll func only if you want to add it
    
    const diceRoll = () => {
    axios.get("https://api.adviceslip.com/advice").then(function (response) {
    // handle success
    setAdvice(response.data.slip);
    });
    };
    
    

    Usually creating custom hooks is a good practice so you can have a cleaner component and you can reuse the logic elsewhere.

    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