don't error when cache value can't be deserialized

The cache is meant to help out by saving old responses. If those
responses do not conform anymore to an updated struct definition, the
whole application should not crash. Instead, the value is silently
ignored and then overwritten by the proper value that has been fetched
from the API.

That way, users don't have to manually clear out the cache if a new API
schema or new features are released.

0 files changed, 0 insertions, 0 deletions