Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What if there is an error duration serializing & deserializing? #43

Open
limbo-lab opened this issue Jan 6, 2016 · 3 comments
Open

Comments

@limbo-lab
Copy link

It seems it has no error handling duration serialing & deserializing.

@dimazen
Copy link
Contributor

dimazen commented Jan 11, 2016

Hello, @limbo-lab! At this moment - nope.
What kind of errors do you need to handle?

@limbo-lab limbo-lab changed the title What is there is an error duration serializing & deserializing? What if there is an error duration serializing & deserializing? Feb 3, 2016
@ollieatkinson
Copy link

@dimazen What if the type returned by the server isn't as expected - I assume outdated clients would want to handle the error gracefully.

Unfortunately I have worked with organisations in the past who provide inconsistent feeds thus it is a requirement to not crash!

@dimazen
Copy link
Contributor

dimazen commented Mar 1, 2016

Hm, for now the only way to handle this is to wrap deserialization into the try/catch, since most of the errors are generated by the KVC. I actually wasn't planning any sort of the errors handling in the next release (the one with Realm support).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants