chore: Add lastUpdatedAt to Task#1875
Merged
Merged
Conversation
Contributor
Author
|
@LucaButBoring FYI |
localden
added
the
rc-high-priority
9 tasks
He-Pin
force-pushed
the
lastUpdatedAt
branch
from
November 23, 2025 09:29
1dc7a6c to
92304cc
Compare
Contributor
|
LGTM, could even maybe reduce it to simply |
Contributor
|
Discussed with @000-000-000-000-000 and @LucaButBoring - this will be the last change for the Tasks SEP that will make it into |
Contributor
Author
|
@LucaButBoring |
000-000-000-000-000
approved these changes
Nov 24, 2025
This was referenced Nov 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Currently, the task only contains
createdAt, the creation time, but the client cannot know the exact time when the task's state transition occurred. We've addedlastUpdatedAtto complete this information, allowing for precise location of a specific state change point during end-to-end troubleshooting, facilitating end-to-end information transmission. Simultaneously, when supporting subtasks in the future, the exact state update time of a subtask will be known, simplifying the implementation of time-sequential logic.How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context