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

Rest-Countries-Api

react
Girma•340
@Girma3
A solution to the REST Countries API with color theme switcher 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 new to react so basically it was nice learning process overall and I would like to use better method to manage state next time.

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

Integrating data that comes from local json file when fetching fail from outside using api call was challenging for me because the object properties are different and I use separate state to mange where the data comes from .

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

Hi Everyone 👋,If you have any feedback, as React is new to me, you are welcome to share it. Thanks in advance for your time!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mahmoud Elagamy•1,100
    @m-elagamy
    Posted 9 months ago

    Hey, I found a few areas that could be improved:

    1- 404 Error on Reload: When I reload the details page of a specific country, a 404 error occurs.

    2- Region Filter Dropdown: The dropdown menu for filtering by region could be improved by automatically closing when a region is selected and highlighting the active region for better UX.

    3- Search Bar Behavior: After searching for a country and clearing the input field, the results remain filtered. It would be more intuitive if clearing the input automatically reset the results to display all countries.

    4- Softening Shadows: The shadows on the header, region filter button, back button, and border countries could be softened a bit for a more subtle and modern look.

    5- Layout: You might want to consider using a container with a max-width to keep the content from growing indefinitely and ensure a more consistent layout on all screen sizes.

    Great job overall! These small tweaks could make your app even more user-friendly.

    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