FX Checker built with Astro

Solution retrospective
I am proud of the improvements I made in my code base by switching from individual components to centralized code.
What challenges did you encounter, and how did you overcome them?Initially I built this with the API code in various Astro components. However, I noticed that I was reusing a lot of code and could probably use the same API call to fill in various parts of the UI. So I built out a library of controllers by referring back to an old Odin project for structure. This helped reduce the code base quite a bit and reduce API calls. Further optimization is required, but this will be easier to update.
What specific areas of your project would you like help with?Any advice on optimizing my display controller would be much appreciated. The file became quite large despite my attempts to optimize by splitting out duplicated functionality to their own functions.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on jkaps9’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