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

REST Countries API with color theme switcher

axios, react, react-router, tailwind-css, vite
Osman•70
@OthmanGh
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 specific areas of your project would you like help with?

Hi everyone,

I've recently completed a project and I'm looking for feedback to improve it. I'd really appreciate your insights on the following areas:

Code Structure & Organization: Are there any improvements I can make in terms of separating concerns, code readability, or file organization?

Performance: Do you see any parts of the code that could be optimized for better performance, especially concerning [specific function/feature]?

Best Practices: Am I following best practices, especially in [insert specific areas like state management, error handling, or API integration]? Are there any common pitfalls I should avoid?

UI/UX Feedback: How does the user interface feel? Are there any enhancements you would suggest for improving the user experience?

Accessibility: Does the project adhere to accessibility standards? If not, what changes would you recommend?

Code Efficiency: Are there any redundant parts of the code or logic that could be simplified?

Security: Are there any potential security concerns or vulnerabilities that I should address?

Please feel free to point out anything else you think could be improved. Any constructive feedback is greatly appreciated!

Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • HANICHE Zahir•280
    @ZahirHaniche-dev
    Posted 11 months ago

    Great project, well executed and completed. Congratulations, my friend.

    I have a very important remark regarding the data reloading with every action you take on the site. I suggest you look at my project to see that the only loading I perform is retrieving the list when we first access the application. In your case, you make API calls every time you process or launch a feature, for example, the filter or the detail page.

    In my case, I use a reducer with a getData function that I call once. Then, for filtering, etc., I manipulate the array that I retrieve as a state.

    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