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

Vue 3, typescript, sass

typescript, vue, sass/scss
paradox•60
@Mateo-Le-Fur
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)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Emmanuel Oloke•320
    @EmmanuelOloke
    Posted over 2 years ago

    Hello Mateo, trust you're doing great. Great job on completing this project, it looks really clean and professional, kudos.

    I do have some observations that I wish to bring to your attention;

    1. When a user clicks on a country card to show more details about the country and then refreshes the country details page, the user is taken back to the Home page as opposed to still being on the country details page that they refreshed on.

    2. On the country details page, there's no state to handle when the country has no Border Countries to display, you can have a div with a text that says "No Border Countries" for example.

    3. Also on the country details page, for countries with Border Countries, the design from Frontend Mentor did show that the country names be displayed in full and also be clickable in order to navigate to the corresponding country, but at the moment only the acronyms of the countries present in the "borders" property returned by the API are being displayed.

    I also had this problem while attempting this challenge some weeks back. A way I was able to solve the issue was to loop over allCountries and also loop over the "borders" property array and check where the borderCountry matches the allCountries.cca3 property, then you can now return the allCountries.name.common value for that country in a separate array. Then use that array to display the border countries.

    That worked for me, you can then go on to add a link to the div that navigates to that particular country's details page. This will fulfill the original design specifications.

    Just thought to bring these to your notice and also share my experience building the same challenge. Hope this has been helpful. Enjoy!

    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