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
I tried to use Parse.1.6.2 and 1.6.4 today but found the when calling query.find.., objects were returned with only the classname and objectId info. All other columns were absent. Eg.
Thank you for your feedback. We use the issue tracker here to track valid bugs in our SDK. Your question seems to be more about how to use Parse. Could you check out the following resources?
You'll notice that in versions prior to 1.6, console.log printed out a bunch of noise and information that complicated debugging (such as listing each object as type c). The new response to console.log is designed to be more straightforward.
I tried to use Parse.1.6.2 and 1.6.4 today but found the when calling query.find.., objects were returned with only the classname and objectId info. All other columns were absent. Eg.
var Plan = Parse.Object.extend("Plan");
var query = new Parse.Query(Plan);
query.equalTo("user", Parse.User.current());
query.find({
success: function(allPlans) {
console.log(allPlans);
...
},
error: function(err1, err2) {
console.log(err1,err2);
}
});
In the success callback the collection printed to the console only contains objectId and className keys.
Is this a bug with the newer versions of this SDK or am I missing something?
The text was updated successfully, but these errors were encountered: