You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
The
safeFetch
andsafeFetchAll
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 returnnull
.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?The text was updated successfully, but these errors were encountered: