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
Every time we save model it also updates createdAt and updatedAt field. We'd expect the createdAt field would not be updated for future object updates.
Code sample:
final batch =Batch()
..save(existingObject);
await batch.commit();
We can use Batch()..update() but the behavior is different. It will update just updatedAt field but on the device it will set createdAt field to null. Is this expected behavior?
final batch =Batch()
..update(existingObject);
await batch.commit();
debugPrint("New Val: ${existingObject.createdAt}"); // here createdAt is null
We believe the issue is here, where createdAt will be set to null:
Every time we save model it also updates createdAt and updatedAt field. We'd expect the createdAt field would not be updated for future object updates.
Code sample:
We can use
Batch()..update()
but the behavior is different. It will update justupdatedAt
field but on the device it will set createdAt field to null. Is this expected behavior?We believe the issue is here, where createdAt will be set to null:
flamingo/flamingo/lib/src/model/document.dart
Line 144 in af8836d
The text was updated successfully, but these errors were encountered: