Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

REST API Countries Switcher with Theme Toggle

react, typescript, sass/scss
Dushyant Goyal•260
@goyal-Dushi
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?

Hi , I am really happy that after I initiated the challenge, I was able to complete it. Although having 3 years of in React, I always learn something new whenever I do such challenges.

I gave my best to keep up with DRY principles and do clean code. But, there always scope of improvement. So, please feel free to suggest or comment anything new that could enhance this project further. I would be happy to work and accept contributions on the same :)

Github Repo : LINK

Project : LINK

Other Challenges completed by Me : LINK

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

I didn't encounter much challenges, only tried to maintain clean code practices and keeping up with the DRY principles.

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

I think enhancing the project by including more challenging features will not only increase my learning curve, but also make the project much better. So, I would really appreciate if you have any new ideas to make this project even better !

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amanuel Chaka•310
    @AmanuelCh
    Posted about 1 year ago

    Hey there @goyal-Dushi

    I liked your approach of using Typescript.

    If there would be any improvements, I would suggest is, give a specified equal amount of width for the country card. I have seen that you are using a max-width of 250px. It would be better if the cards have a uniform width. The error might also arise from the ⁣card image because the API doesn't respond with a same image width for all countries. So handle the image width too. Plus, give a lighter box-shadow for the cards. Besides that, it was nice ✌

    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
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