This PR adds a workaround that stores precipitation data from minutely forecast. A onecall JSON response that contains a minutely array uses the precipitation key instead of rain (to save on data) looks like this:
This solution takes the precipitation field and copies it to the rain field if rain wasn't already set. The result is that the precipitation data ends up in the rain field encapsulated in a dict like: { 'all': <precipitation_value> }.
This PR adds a workaround that stores precipitation data from minutely forecast. A onecall JSON response that contains a
minutelyarray uses the precipitation key instead of rain (to save on data) looks like this:This solution takes the precipitation field and copies it to the
rainfield ifrainwasn't already set. The result is that the precipitation data ends up in the rain field encapsulated in a dict like:{ 'all': <precipitation_value> }.Fixes #343