-
-
Notifications
You must be signed in to change notification settings - Fork 206
ParseFile seems to not handled in ParseObject _canbeSerialized function #242
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
Comments
I also have the same issue: plan.set('name', name);
plan.set('text', description);
plan.set('startedAt', start);
plan.set('endedAt', start.add(Duration(days: (7 * duration))));
plan.set('minRepetition', minRepetition);
plan.set('isTemplate', false);
plan.set<ParseObject>('user', user);
final response = await plan.save();
if (template != null) {
await _createPlanItems();
}
|
I now also have this problem for some reason. I seem to have had a null value in some nested field. from parse_object.dart bool _canbeSerialized(List<dynamic> aftersaving, {dynamic value}) {
if (value != null) {
...
} else if (!_canbeSerialized(aftersaving, value: _getObjectData())) {
return false;
} It seems like even what the object is null it tries to rerun the _canbeSerialized with _getObjectData(), which should return and empty map when the object is null. Not sure if this happens correctly. |
We are closing issues that have been open for a long time without activity. |
L221 of parse_object.dart
if (value is ParseObject) {
if (value.objectId == null && !aftersaving.contains(value)) {
return false;
}
}
when value is ParseFile, it does not have objectId, but it does not mean it is a new unsaved object, which is the intention of the null check here.
My object that contains ParseFile seems to have infinite saving loop here.
Am i using it correctly or is it a bug here?
Thanks!
The text was updated successfully, but these errors were encountered: