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
Arrow didn't have error handling (on purpose) but this is something we can discuss. Having given this some time I think it might not be worth it. I personally never had the need to test errors in JSON parsing as I believe that this is an Api-side problem.
On the iOS side, Unit tests test against local JSON files to make sure parsing works as expected.
On the backed side, unit tests test that the api sends the correct JSON structures.
Could you elaborate on a concrete case where we need to catch parsing errors?
@s4cha agreed, I don't have such use cases either. For me it works perfect just to do nothing if the key is not there or could not be parsed. Other frameworks usually provide a way to specify a fallback value for that case.
Find a way to get notified if a parsing error occurs, for example a missing key
The text was updated successfully, but these errors were encountered: