Hi all!
I am developing a Rust app that’s basically a weather dashboard (mostly to learn to use generative AI in coding) and today I noticed a lot of issues when pulling from the better_forecast endpoint. Most commonly, the timestamp would be missing from the head of the JSON payload but often other values (UV popped up more than a few times as missing) would be missing, and my json parser, expecting those values, would puke and abort, leading to a lack of data to display on the dashboard. As far as I could tell, this was on the API side; both my functional production code and my dev code was exhibiting the same behavior with the same missing values, and when I went to the endpoint myself and grabbed the JSON, those values were indeed missing despite being documented as non-optional fields in the API documentation. Any clarity is appreciated! (In any case, it prompted me to implement forecast caching so that I can absorb short outages so net positive result. https://gitlab.com/alostengineer/tempest-wx-interface/ for anyone interested.)
Thanks!
1 Like