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
When creating a new document through the dashboard example, the updatedAt value is not displaying correctly in the document list. (Ref: yorkie-team/dashboard#99)
What you expected to happen:
When a document is first created, the updatedAt should be set to the same value as createdAt.
Reasons for this approach:
Initial state indication: It clearly shows that the record has not been modified since its creation.
Data consistency: All records will have an updatedAt value from the moment of creation.
How to reproduce it (as minimally and precisely as possible):
Navigate to the dashboard
Create a new document using the provided example
Check the document list
Observe that the updatedAt value is not correctly set
Anything else we need to know?:
Environment:
Operating system:
Browser and version:
Yorkie version (use yorkie version): 0.4.30
Yorkie JS SDK version: 0.4.28
The text was updated successfully, but these errors were encountered:
Hello! I've identified an issue that needs fixing:
While working on this pull request, I realized that updated_at is only being updated when there's an operation in Change. This explains why updatedAt isn't set when a document is created.
I apologize for my mistake and will fix it immediately.
What happened:
When creating a new document through the dashboard example, the
updatedAt
value is not displaying correctly in the document list. (Ref: yorkie-team/dashboard#99)What you expected to happen:
When a document is first created, the
updatedAt
should be set to the same value ascreatedAt
.Reasons for this approach:
updatedAt
value from the moment of creation.How to reproduce it (as minimally and precisely as possible):
updatedAt
value is not correctly setAnything else we need to know?:
Environment:
yorkie version
): 0.4.30The text was updated successfully, but these errors were encountered: