5 replies

`_creationTime` issue for `withOptimisticUpdate`, and thoughts

Say I have a

messages

messages

list to display and I need to show the

_creationTime

_creationTime

for each of the

message

message

Once I have inserted a

message

message

and I want to show the message immediately instead of waiting for a api call.

1.

withOptimisticUpdate

withOptimisticUpdate

is used on the

api.messages.insert

api.messages.insert

mutation, updating the

api.messages.list

api.messages.list

query.
2. Inside

withOptimisticUpdate

withOptimisticUpdate

, I have to set

message._creationTime = clientSideNow()

message._creationTime = clientSideNow()

, and display the time.
3. Since the

OptimisticLocalStore

OptimisticLocalStore

is fully clientSide and temporary, after the server have finished the real mutation, the newly inserted message will be updated to

message._creationTime = serverSideNow()

message._creationTime = serverSideNow()

.
4. If there is any network latency, the message list UI will experience an unexpected update because of the date change.
5. Same situation for

message._id

message._id

.

Workaround1: Add my custom

message.localFirstCreationTime

message.localFirstCreationTime

, which is generated and passed from client side.
Workaround2 as a feature request: allow overriding at least

_creationTime

_creationTime