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
As stated in #420 when we query parse objects including sub objects that are related in the query altought the response gets full data (using livelist, for normal queries I'm facing issues as in #615 ) when we print or use toString() in the ParseObject the related objects doesn't come with full data in the json.
It would be very helpful if the json came with these additional columns because it could be used in map functions.
I've found a way to do it, using toJson(full: true) from the ParseObject, but this gives lint errors that I need to ignore (because toJson is protected in the class).
As the toString() method from ParseObject just encapsulate the toJson, it would be helpful if it had the same parameters as to Json or if toJson wasn't protected.
The text was updated successfully, but these errors were encountered:
Hi,
As stated in #420 when we query parse objects including sub objects that are related in the query altought the response gets full data (using livelist, for normal queries I'm facing issues as in #615 ) when we print or use toString() in the ParseObject the related objects doesn't come with full data in the json.
It would be very helpful if the json came with these additional columns because it could be used in map functions.
I've found a way to do it, using toJson(full: true) from the ParseObject, but this gives lint errors that I need to ignore (because toJson is protected in the class).
As the toString() method from ParseObject just encapsulate the toJson, it would be helpful if it had the same parameters as to Json or if toJson wasn't protected.
The text was updated successfully, but these errors were encountered: