Setting it via API prevents various race conditions, where server last modification date is different from what the client has, potentially overriding other clients' data.
This means Amber stops updating lastmod internally and instead accepts it as a settable field.
This affects POST /task and PATCH /task/[id].
Setting it via API prevents various race conditions, where server last modification date is different from what the client has, potentially overriding other clients' data.
This means Amber stops updating `lastmod` internally and instead accepts it as a settable field.
This affects `POST /task` and `PATCH /task/[id]`.
tdemin
Setting it via API prevents various race conditions, where server last modification date is different from what the client has, potentially overriding other clients' data.
This means Amber stops updating
lastmodinternally and instead accepts it as a settable field.This affects
POST /taskandPATCH /task/[id].Make lastmod settable via APIto API v0: make lastmod settable via API 3 years ago