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

REST Countries API Using Vue 3 + Composition API

Aaron Romanick•270
@aaron-romanick
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 was a fun challenge and I decided to use Vue 3 for the first time (I've used Vue 2 up until now). With the new Composition API I was able to make a native data "store" much like Vue 2's Vuex. I also took my first crack at using Grid layouts for the country details pages.

  • Since some countries' names are so long, I set a text-overflow value along with overflow: hidden in the CSS so the button sizes wouldn't be all over the place. The title attribute has the full text, but I'm wondering if this is okay from an accessibility standpoint. Any suggestions would be appreciated.
  • I wanted to make the whole country "cards" clickable; however, it doesn't work if you click on a blank area of the card. If you know how to make it so the entire card is clickable, I would love some feedback?
  • I'm not happy with how I ended up dealing with the loading of border countries since I couldn't get the reactivity to work while the Country component is active. Instead, I am switching to the Loader component until the extra country's details are loaded and then switching back. I'd like to just reactively switch between the countries while in the Country component, but I kept getting undefined errors because I couldn't get the computed property to run for that. If you have any suggestions, I'd like to hear them.

If you have any feedback/comments, particularly with how I handled the Composition API of Vue 3. Of course, other comments on other aspects would be great too!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Aaron Romanick'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 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.