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

Advice App Using React and SCSS

bem, react
Hamzat Lawal•560
@EngineerHamziey
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Seniors, this is my first react project. I Have been so busy at work that It's hard to find time to learn, kindly help me to review this solution.

Here are my questions:

  • Do I always have to set dummy values for states before data arrive from the API like I did here?
 const [advice, setAdvice] = useState(
    {
      "slip": {
        "id": 0, 
        "advice": ""
      }
    }
  )
  • Is there any details I am missing in the UI?
  • kindy go through my react code, what should I improve on?
  • what do you think of my BEM class name usage? am I getting it?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • visualdennis•8,375
    @visualdenniss
    Posted about 2 years ago

    No, you don't have to set a dummy data with the corresponding object structure.

    I've set it so in mine e.g.: const [advice, setAdvice] = useState('Click on Dice below to get an advice')

    You can also set useState("") etc. Just make sure if you are expecting array or object, do not try to read data before it is there. For example if you expect an array of objects, and then in your JSX, if you use map method like data.map((item)=> item ), you'll get error of cannot read property of undefined, because it'll try to render initially when you data has not being fetched and put into state yet. But you can fix that usually with data?.map or {data && data.map()}

    Hope you find this feedback helpful!

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub