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

REST Countries API (React, useContext, Axios, Material UI, TDD)

accessibility, axios, cypress, react, react-router
Aman Singh Bhogal•1,010
@asbhogal
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


Several changes and additions have been made to this solution from the brief for improved UI:

  • A 'View More' pagination button which displays the next 20 countries each time
  • Automatically alphabetized country lists on first render
  • Live filtering of country search with each keystroke entry
  • Mapping of border country codes to the respective countries
  • Increased font size for grid container text (population, region and capital props)
  • Displaying the name of the region selected in the top right menu

Stacks and Tools Used

  • React (custom context and hooks)
  • Axios
  • Material UI
  • Cypress Unit Testing

Linting

  • ESLint

Planned Future Iterations

  • Review of component and Unit Testing w/ Material UI providers
  • Addressing of DOM depth attributing to minor performance dips on first render
  • Addition of 'clear' on filter menu selection to reset to viewing all countries
  • Disable Vercel compression image assets (owing to visual degradation)
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 Aman Singh Bhogal'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 1st-party linked stylesheets, and styles within <style> tags.

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.