Weather component

[Bryce-Soghigian]

Description

Add attribution link to Readme and code

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Change status

• Complete, tested, ready to review and merge
• Complete, but not tested (may need new tests)
• Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

Please describe steps taken to ensure this feature is functional and does not break other features:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation, if relevant
• I have run the app using my feature and ensured that no functionality is broken
• My changes generate no new warnings
• There are no merge conflicts

[Bryce-Soghigian]

At first Prettier may seem to make more of a mess of the codebase than it fixes, but I think adding this prettier config will lead to consistent code styling throughout our codebase!

I am rewriting the entire weather component due to the API that the previous team was using being depreciated.

I also added a loading spinner into utils so that we can use that throughout our application if need be.

[Bryce-Soghigian]

This piece of code takes our coords we get and feeds them to a reverse geocoding api to fetch the city location