Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support to extract the 'timezone' property now returned from the openweather API:
https://openweather.co.uk/blog/post/we-have-integrated-time-zones-our-weather-api-products
Includes
Notes:
The fake data files had to be updated with timezone keys for existing tests to pass. It currently would fail should 'timezone' not exist in a response, but it doesn't look like other properties are checked for existence either so I've ignored that on the basis all responses appear to have a timezone now.
I've hard coded the 'population' constructor argument to null as I didn't want to remove it, but the population doesn't appear to exist in any responses to pass it through (it seems to be currently skipped by all construction). If population is never used it might be neater to remove it and put timezone in its place, but that feels like a potentially separate discussion / fix, albiet one that might be easier to do before adding this...