Skip to content

fix: If there was no chat description, and it's set to be an empty string, don't send out a "chat description changed" message#7879

Merged
Hocuri merged 1 commit intomainfrom
hoc/fix-set-empty-chat-description
Feb 23, 2026
Merged

fix: If there was no chat description, and it's set to be an empty string, don't send out a "chat description changed" message#7879
Hocuri merged 1 commit intomainfrom
hoc/fix-set-empty-chat-description

Conversation

@Hocuri
Copy link
Copy Markdown
Collaborator

@Hocuri Hocuri commented Feb 23, 2026

fix #7877

The bug was: If there is no chat description, and the chat description is set to an empty string, the INSERT statement inserted a row with an empty chat description, and therefore from the view of the INSERT statement, something changed.

This PR fixes this by simply loading the chat description first, and comparing it.

…ring, don't send out a "chat description changed" message
@Hocuri Hocuri merged commit ff70235 into main Feb 23, 2026
30 checks passed
@Hocuri Hocuri deleted the hoc/fix-set-empty-chat-description branch February 23, 2026 11:37
@r10s
Copy link
Copy Markdown
Contributor

r10s commented Feb 23, 2026

ftr, successor of #7829

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

if description is empty, don't consider it changed the first time

3 participants