Should safeFetch helpers also be safe from decoding errors?

[lorisleiva]

The safeFetch and safeFetchAll helpers from the JS renderers are currently safe from accounts that are missing on-chain. That is, if the account is missing, the function will return null.

However, if the account exists but the fetched account doesn't follow the expected serialisation of the account, this function will fail instead of returning null.

Is this the expected behaviour? Should we also allow accounts that are not following the correct serialisation to return null? How safe should these safeFetch helpers be?

[4lve]

I would like them to be super safe by default due to the safe prefix