[object Object] bug?
dmalan opened this issue · 5 comments
This suggests the name of the bottom incident was an object not a string somehow, which might've been a glitch in statuspage's API at the time this incident was fetched? I'm literally storing the value they give back, which they promise to be a string per http://cs50.statuspage.io/api#incidents. The top incident supports this claim since it got stored the same way, and yet it got rendered correctly.
Want me to check whether it's a string before storing it and maybe log it to the console if not? This means we might miss some incidents, but we should be able to see what we got back from statuspage in case this happens again.
I wasn't able to replicate this, so I don't have a sample object of what we got back, but I'll ask them if it's possible for it to ever be an object instead of a string.
Should be fixed.
