Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive Dictionary Web App

react, axios
Bhoami K Khona•360
@bhoamikhona
A solution to the Dictionary web 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 am fairly new in terms of using React so the fact that I was able to complete this project makes me feel proud. It was definitely challenging for someone who is a beginner. I am still learning about redux and context so, next time that I make this project, I will probably end up using one of those two.

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

My biggest issue was when I set the initial state of data to null.

I wanted to set "keyboard" as the initial value and then use the useEffect hook to call the API to get its data when the page first renders but, I was facing a lot of errors regarding it. For this I saw a few YouTube videos, and googled online along with checking out some Stack Overflow queries however, I am still not sure what is going on. So, I will continue my research on the topic.

Another issue was passing data as props from one component to another. I used async-await before I got the data and for some reason when I passed the data from one component to another, and tried destructure the data there, I got an error. For this, I asked one of my acquaintance to help me figure out why that was happening, and I got to know that when I pass data to another component, I need to check if the data is null in that component before using it. Which is something that I find weird so, I mean to do some more research about it.

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

Honestly, it would be great to have feedback on anything. Like I said, I am a beginner in ReactJS and I am sure there is a huge room for improvement so, any constructive feedback would be greatly appreciated. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Bhoami K Khona's solution.

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.