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

List Of countries with REST API

react, sass/scss
OffixialTrust•160
@OffixialTrust
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?

It’s my first time building a multi page project (don’t know what they call it SPA when it’s clearly MPA). I’m proud of myself, as I’m improving my ReactJS skills

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

The challenges are too many to mention. How I overcame? Well… let’s say it helps to have a quality support system and networks.

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

Any advice will be helpful. And yes I didn’t use the best of the “best practices”.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan Heslop•2,440
    @dylan-dot-c
    Posted 4 months ago

    Hey well done with this challenge it looks excellent!

    I think there are a few things to improve

    • Firstly accessibility. I see why you have an handle navigate function to programmatically change the route on click, but one draw ack is accessibility, like a user limited to their keyboard won't be able focus on that country and cant click on it. One solution is to wrap it with an anchor tag so that will be presented as a focusable link.

    • I realized you had a json file with all the countries, and while that ain't a bad approach, it would be good approach to use ajax or just fetch to get from the real API, and use other API endpoints to get the specific country, instead of passing in the data down(still isn't a bad idea and you don't have to worry about the countries API failing).

    • I think you can look up tanstack query to see another way of fetching data from an API.

    Anyways, take a look at my solution did it awhile so forgive the react code, I need to update some things. But tell me what u think

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