-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Idea] Callback with ParseException #37
Comments
Okay so this is definitely something we can do. I did originally take this approach but then removed it as it added a lot of boiler plate code... however, after writing my own app using this library, I do feel that it's something that is needed. This will be a breaking change but will be added. I'm not 100% when the ParseUser queries will be added, but a ParseResponse object can be the return type for a ParseUser request. |
You were correct in this idea and this has now been implemented. It's on the develop branch and will be released with 1.0.6. If you check the updated example code, there's now examples of the user being returned as a ParseResponse which contains user and exception details. There's also a working example of a query based on a user. |
Hi,
I think it could be a good idea if for maybe most of functions (#, reset password, cloud codes functions, etc.), we can have a callback with firstly the object(s) and secondly the ParseException, like this example (from the official docs: https://docs.parseplatform.org/android/guide/#retrieving-objects) :
And
With this, if we # a user and there is an error, we know which error is because for the moment, we can't know why it fails.
The text was updated successfully, but these errors were encountered: