-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nil Values #58
Comments
Ah damn. I thought things were ok with the unit tests. I’ll take a look at this later this evening and try to submit an update ASAP. |
Ok thanks! |
I'm currently working on this, and I realized that the JSON keys for some of the precipitation values differ from the property names I specified, which explains that issue. Are you seeing other data that exists in the JSON but not in ForecastIO? I'm searching for other errors but not coming up with much. Additionally, |
I think it was mainly precipitation and temperature high / lows were the main problem, but I didn't have time to investigate into too much detail. |
I checked the temperature values, and I was able to confirm that those fields are being populated. They are optional properties, so they may not always be there on all requests. The main issue I saw was with the precipitation properties, which are now fixed in 6.0.1. Let me know if you run into more discrepancies between the JSON response and ForecastIO, and thanks for bringing this to my attention! |
Ive noticed since updating to the latest version a lot of values are now nil all the time. All the precipitation values, temperatures low/high etc. Some data is being decoded but not all of it.
The text was updated successfully, but these errors were encountered: