Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Second Attempt at REST Countries API. App now uses only 1 API call.

react, fetch
Gareth Carter•235
@gcarter89
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


This is my second submission for this challenge.

While I fulfilled the brief for the project, I wanted to give myself the additional challenge of fulfilling the requirements using a single call to the API.

Rather than calling the API multiple times for fetching country details and when navigating back to the main list of countries. I wanted to have one persistent piece of state that could manage everything.

In the previous submission, I found myself dealing with bad request handling. After a number of calls - potentially down to API call throttling. I found a single call to the API satisfied everything I needed to do. It's made the initial load a little longer, but the navigation and use of the app, very fast afterwards. I'll probably filter the fields in each API request later.

In my next submission, I'll look at component-ising things more!

Any questions or improvements, let me know!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dark-Lover•735
    @Dark-Lover
    Posted over 3 years ago

    i like your solution

    what u said is what everyone should do, minimize as possible api calls, cuz in real world projects more requests means paying more money. and in this project a single call is enough, u can then filter from it all the data u need in every component.

    keep coding

    Marked as helpful
  • Hexer•3,620
    @EmmanuelHexer
    Posted over 3 years ago

    Great job overall man. Keep it up

    • One tip i can give you is to always read the reports at it will help you know the issues in your code ,so that you fix it.
    Marked as helpful
  • Daniel Ginting•100
    @daniel-ginting
    Posted over 3 years ago

    Mine only call once.

  • MatiX•360
    @MatiX221
    Posted over 3 years ago

    Firstly you should read reports.

    Secondly you can't unselect continent filter, so if you select europe you can't set it to all.

    And thirdly if you have something in search bar and then change region in continent filter. It will show all countries from that continent and not country that you searched from that continent.

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.

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

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