fix: update workspace chat lastUpdatedAt - #6288
Open
AbarnaaSree wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Pull Request Type
Relevant Issues
resolves #6282
Description
This PR fixes the workspace chat
lastUpdatedAtfield not being synchronized when an existing chat is updated.The
WorkspaceChats._update()method now automatically setslastUpdatedAtto the current timestamp while preserving the existing update data.A regression test has also been added to verify that
lastUpdatedAtis updated correctly.Visuals (if applicable)
Not applicable — this is a backend change.
Additional Information
The change is limited to the workspace chat update flow and does not modify the Prisma schema.
Developer Validations
yarn lintfrom the root of the repo & committed changes