Forecast search #4

[Kate-v2]

Description

• Seach Bar has placeholder text to indicate what should be entered. API is scoped to US cities, but is very flexible on what it accept - example: "denver" vs "denver, co" still returns Denver. Some city-names are in more than one state, so when the Forecast is displayed, the state will be printed. If the returned location was not as expected, the user can enter a more specifc search, but that's up to them. NOTE: 'bloop' a fake city, for some reason returns a real (but differently named) location; random character (kjskfja knfdnf) does not return a location and a ...
• location SAD PATH gives feedback to the user to check their spelling or try a new location.
• Reusable Function for making Request
• Forecast API is functional
• No tests yet

---

Issues # and Action

closes #4

---

TO DO / Noteworthy

• Notes where things can be refactored
• Notes for edgecases / micro expereinces to be added later
• Issue #12 is for the actual display of information and will be opened next.

---

Features

• [x] New Feature
• [ ] Expand Feature
• [ ] Optimize/Improve Feature

---

Testing

• [x] No Testing

• [ ] Some Testing

• [ ] Sufficient Testing

• [ ] I have left notes near functions that have not been tested

• [ ] I have included intentionally skipped / failing / empty tests as a reminder to add/improve these later

• [ ] Tests have been changed

• [ ] Existing tests are now failing / skipped

---

Deployment

• [ ] This is a complete feature, ready for deployment
• [x] This is a partial feature, NOT ready for deployment

---

API Changes

(please detail in description)

• [x] New API

• [ ] Existing API, New Endpoint

• [ ] I have updated the README.md

---

Tech Changes

(please detail in description)

• [ ] New Functional Library

• [ ] New Testing Library

• [ ] New Debugging Tool

• [ ] I have updated the README.md