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

REST Countries API with color theme switcher solution-pure Javascript

sass/scss
yishak abrham•2,150
@yishak621
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


heloo community

Even if building a web app is easy with frameworks i used pure Javascript tools to build this webapp. i used module type JS to enable building different components(9) of JS and combining them in to one JS file. crucial components

  • formatNum.js/formating population number
  • setCountry.js/adding the clicked country name in to local storage(enable to acess it after we are redirected to the single country page)

Cool methods

1 - using ...new Set method to return the unique values from the data[in these project to grab the unique continents ] instead of using reduce method its easy 2 -format number --recive a number and format it to the thousends formats

function formatNum(number) {
  let nf = new Intl.NumberFormat('en-US');
  nf = nf.format(number);
  return nf;
}

3 - Object.values(objname)[index] method to grab the first item of object from the teration, even if the property name is not consistent for all of iterable objects

const newnativeName = Object.values(nativeName)[0].official;

finally

i do my best to make it responsive and it looks good for me ....as usual if u have a better way of doing these project please leave a comment ....and also if u have difficulties doing these project u can refer my codes i elaborate details of it as a line comment in JS.. Thank U!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • yanyan_alien•170
    @yanyan-alien
    Posted over 2 years ago

    Hi!

    Congrats on completing this!👍Cool animations on the theme switcher button and the back button! ✨Also props to you for thinking of having a back to top button on this very long site

    These are some of the stuffs I noticed when browsing through your live site:

    1. After the user sets the page to dark mode and clicks on a particular country detail, the page will be back to light mode. Maybe you can use localStorage.getItem() and localStorage.setItem() to store and retrieve the set theme
    2. The sticky navigation bar doesn't occupy the whole screen width when the screen is wide (eg. 1400px)

    Good luck! 🎉

    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