REST Countries API + React + React Router + Context API
Design comparison
Solution retrospective
Hi everyone 👋,
Thanks for having a look at my project. 🚀
I'm proud I actually completed this project. This was a challening one as the instability of the API was the most frustrating part. Once that was resolved, I could focus on the actual functionality of the app, and this turned out to be one of the most complex projects I have completed to date. This was my first time using React Router and the Context API in React, and although a bit confusing in the beginning, I was able to get everything to work eventually. I'm specifically proud of how I was able to process and work with the data as the payload from the API is quite large and has a few dimensions to work through.
What challenges did you encounter, and how did you overcome them?As mentioned above, making use of the API proved to be very frustrating and almost made me abandon this project. I didn't really want to make use of the JSON file provided, so I needed to come up with a creative solution. I resorted to trying to only become dependent on one successful API call, and once that was successfully retrieved, I stored it into the users sessionStorage from which point the data was handled from there to prevent downtime when using the app. Once I got past that, the challenge become working with the data but making a point to keep as much of the logic inside the CountriesContext file I created.
What specific areas of your project would you like help with?I'm open to any and all feedback. 📝
Community feedback
Please log in to post a comment
Log in with GitHubJoin 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