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

Integrating with a REST countries API

react, tailwind-css, react-router
hakeemgardner•170
@hakeemgardner
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


I found it difficult to get the countries flags to be the same size and also some aspects of the countries details are missing. I'm unsure about that aspect. also i would like to know what areas can be improved about

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Better5afe•850
    @better5afe
    Posted almost 2 years ago

    Hi there, congrats on completing the challenge!

    Below you can find some minor suggestions from my side:

    • The Where in the world page title can be a Link element that takes the user back to the Homepage onClick.
    • You can add some space between the moon icon and the button text. Also, you can add flex to it and align the icon and the text to be on the same line vertically.
    • Detail pages for some countries are not found (see Antarctica or Western Sahara).
    • You can add a feedback message that no countries were found if the user types in an incorrect value.
    • No results appear if the user selects the America filter.
    • There are some issues with the detail fields, such as empty Currency and Languages and the Top Level Domain is always displayed as "none".
    • For the Population field, there is a method to automatically add comas to larger numbers - you can try implementing it!
    • I see that you are fetching the data inside the App component and then providing it to other components by props drilling. As an alternative, I would suggest Redux Toolkit for state management as this app is quite complex and for fetching the data you can use either Redux Thunk or React Router's loader functions.
    • As for the image size issue, you can set a width on the entire card element and then make the image container take 100% of this amount. Tried it in the browser and it seems to work.

    Overall, I really like your approach. The code is well written and organised. Keep it up!

    Happy Coding!

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