This repository is a code exercise for Refersion by Mike Taylor, Feb 22, 2021
Download the design Sketch file: (or PDF ).
In the Sketch file, you’ll see the design along with a duplicate containing notes which detail the data that should be used from the API response. For example “name”, refers to object.
To get the current data, please use this API: openweathermap.org
The API also provides an icon code. The mapping is described . For example, a code “10d” would link to this icon.
Your React app should call this API upon load or when the button is clicked, be well organized (.jsx, .css, .scss files etc.), and be able to run locally with minimal effort (usually via an “npm build” command defined in a package.json file).
That the design is pixel-perfect. Elements like fonts should match, margins/paddings should be identical to the Sketch design as possible.
Your JS code should be well organized and logical. A bad implementation would be unnecessary nested if-statements, as an example.
- Initial code cleanup performed using VSCode Extension (nomadjsdev.cra-tasks-after-init)
- Includes basic Jest tests included with CRA, modified for this app.
/src/Components/index.jsis used to keep 'private' and 'protected' components separate.- --While developing the calls to the API, a loop was created that overran the quota for the app. I am receiving the error
GET https://api.openweathermap.org/data/2.5/weather?zip=10036,us&appid=709847967f5e54b97308c1b2cae4dee5 429 (Too Many Requests)-- - The temperature data from the API is off by +200º. I have made an adjustment in the code, but this is a hack.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify