Right now, when we experience a decoding error, we receive a very vague message that doesn't give us much in terms pinpointing the offending param, so we end up adding handling for this on a per-app basis by unwrapping the decoding error type and context. This seems like something that is likely to be similar across apps and that Netable is well set up to abstract for us.
Right now, when we experience a decoding error, we receive a very vague message that doesn't give us much in terms pinpointing the offending param, so we end up adding handling for this on a per-app basis by unwrapping the decoding error type and context. This seems like something that is likely to be similar across apps and that Netable is well set up to abstract for us.